Redis is an open source, in-memory data structure store, used as a
database, cache and message broker. Our integration pulls in
statistics from the Redis
INFO command for comprehensive and
complete Redis monitoring.
The Librato Agent allows you to easily monitor the health of your Redis service(s). We gather statistics from the Redis INFO command and emit them to your Librato account, along with your other server metrics.
The Redis 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 Redis icon in the integrations catalogue.
Toggle the Enabled switch to activate the Redis integration on your Librato account and create the preconfigured Redis Space.
At this point your integration is complete and any Redis metrics associated with this integration will be allowed through your Librato Agent service-side filters.
By default, Redis listens on localhost port 6379. If necessary, this can
be adjusted in your
LoadPlugin redis <Plugin redis> <Node localhost> Host "localhost" Port "6379" Timeout 2000 </Node> </Plugin>
Note: You must restart the agent after any changes to your Librato Agent configuration files.
$ sudo service collectd restart
At this point you should begin seeing
librato.redis.* metrics in your Librato account.
Filtering by Node¶
This plugin is optimized for the Librato monitoring service. Besides
simply gathering all of the service metrics made available via Redis’
INFO command, we normalize the metrics so that the service Node (as
redis.conf) is appended to the metric source. By
default we set this value to
localhost, although you can edit this
value (or add more services) and Librato will automatically append the
Node string to each associated metric source. This makes it easy to
leverage Librato’s dynamic source
feature across your fleet of Redis 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.