Monitoring of INFO metrics

[David Gwartney]

I work for SaaS monitoring company. I am building a plugin that will work with our agent to monitor Redis. What are the essential metrics that need to be collected from a Redis instance to monitor the instance's performance.

If by chance you are not familiar with the info command here is a link to the documentation:

http://redis.io/commands/INFO

Dave

[Marc Gravell]

The things that are most useful to me (not all of them are in "info", but all are possible):

used memory, ops/sec, client count, role, slave count, last save, slowlog, latency perceived from the client, replication backlog if a slave, version, uptime

--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
To post to this group, send email to redi...@googlegroups.com.
Visit this group at http://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.

--
Regards,

Marc

[Shane McEwan]

G'day!

I monitor: changes_since_last_save, total_commands_processed,
connected_clients, connected_slaves, total_connections_received,
expired_keys, keyspace_hits, keyspace_misses, db0_keys, db0_expires,
mem_fragmentation_ratio, rdb_changes_since_last_save, role,
master_last_io_seconds_ago, used_memory, used_memory_rss.

Useful metrics for monitoring performance are: total_commands_processed,
keyspace_hits, keyspace_misses

Useful metrics for health alerting: (role=master and
connected_slaves=0), (role=slave and master_last_io_seconds_ago>30),
mem_fragmentation_ratio is probably a good one too but I don't know at
what value I should be alerting at!

Shane.

[Rémi Coll]

I work on a redis-exporter, it's a tool which grep Redis metrics and expose them as TimeSeries over an http endpoint, if it can help you : https://github.com/miton18/redis-exporter

I used it with a Beamium which send metrics to a Warp10 server. ;-)