AWS CloudWatch local monitor agent
20 June 2014
When you manage an online application one the most important thing is resources monitoring in order to collect and understand internal metrics of your application and trigger alarms in case of problems (close feedback loop -> machine to machine networks). AWS CloudWatch is an interesting starting point but effectively send all your events directly to the cloud monitor can impact on your application.
For that reason i have started a new project that runs locally and listen for incoming messages, collect them and sent periodically to AWS CloudWatch.
The agent is listening for incoming UDP/IP packets on localhost, it collects and shrinks all data received in order to publish only results to AWS CloudWatch.
All messages are JSON objects that indicates the “namespace”, “metric name” and the metric “value” in this form (from 0.0.6 you can also put the unit and the operation type):
The UDP/IP simplify all the communication problems and the datagram protocol create a sort of sandbox for the application that can send packets also in case of agent problems and failures (no guarantees on packages loss). The agent is designed to run locally (and only locally), in that way we can, reasonably, skip the UDP/IP packet loss problems.
The long running process is written in Go. In that way i can control all the concurrency needs of the agent and separate processes and obtain a very high performances (300k # per minute on a m1.small instance).
You can find the daemon here (local lagent)
For PHP application i have written a simple client library
Here you can find the PHP client library project