Memcached is an open source, high-performance, distributed memory
object caching system, generic in nature, but intended for use in
speeding up dynamic web applications by alleviating database load. Our
integration pulls in statistics from the Memcached
for comprehensive and complete Memcached monitoring.
The Librato Agent allows you to easily monitor the health of your Memcached service(s). We gather statistics from the Memcached stats command and emit them to your Librato account, along with your other server metrics.
The Memcached integration depends on the Librato Agent. If you haven’t already, you will first need to install the Librato Agent. Once this is complete, select the Memcached icon in the integrations catalogue.
Toggle the Enabled switch to activate the Memcached integration on your Librato account and create the preconfigured Memcached Space.
At this point your integration is complete and any Memcached metrics associated with this integration will be allowed through your Librato Agent service-side filters.
By default, Memcached listens on localhost port 11211. If necessary,
this can be adjusted in your
LoadPlugin memcached <Plugin memcached> <Instance "local"> Host "127.0.0.1" Port "11211" </Instance> </Plugin>
Note: You must restart the collectd service after any changes to your Librato Agent configuration files.
$ sudo service collectd restart
At this point you should begin seeing
in your Librato account.
Filtering by Instance¶
This plugin is optimized for the Librato monitoring service. Besides
simply gathering all of the service metrics made available via
stats command, we normalize the metrics so that the
service Instance (as defined in
memcached.conf) is appended to
the metric source. By default we set this value to
you can edit this value (or add more services) and Librato will
automatically append the Instance string to each associated metric
source. This makes it easy to leverage Librato’s Dynamic Source
feature across your fleet of Memcached services.
Visit your preconfigured Space to observe your new metrics as they stream in. You can use our dynamic source field at the top to filter your view to a subset of metric sources. For example, you may want to isolate the view to a specific tier of web servers or even to an individual machine that is behaving badly.