Every cache sends its engine metrics to its project in Observability, free and
automatically: there’s nothing to install or turn on, and they aren’t billed or counted against
Observability’s limits. They arrive every 30 seconds, with the cache’s ID as the cache label.
Dashboard
The cache’s Monitoring tab in the console shows a built-in dashboard for its engine: memory, hit
ratio, evictions, connections, commands per second, the standby’s lag, and on Valkey, persistence;
on Memcached, items and bytes. Viewing it needs obs.metrics.query.
Metrics
Metrics have the names the widely used open-source redis_exporter (Valkey) and
memcached_exporter (Memcached) give them. They carry the labels cache and role. Take the
maximum over role, for example max(sum by (role) (…)), so a query keeps working through failovers.
| Engine | Examples |
|---|---|
| Valkey | redis_memory_used_bytes, redis_memory_max_bytes, redis_keyspace_hits_total, redis_keyspace_misses_total, redis_evicted_keys_total, redis_connected_clients, redis_commands_processed_total, redis_aof_last_bgrewrite_status, redis_rdb_last_bgsave_status |
| Memcached | memcached_up, memcached_current_items, memcached_current_bytes, memcached_limit_bytes, memcached_items_evicted_total, memcached_current_connections, memcached_commands_total (by command and status) |
Valkey’s metrics keep the redis_ names, which Valkey shares.
# Hit ratio over 5 minutes
max(
sum by (role) (rate(redis_keyspace_hits_total{cache="cch_4k2m9x0a7qpe"}[5m]))
/ (sum by (role) (rate(redis_keyspace_hits_total{cache="cch_4k2m9x0a7qpe"}[5m]))
+ sum by (role) (rate(redis_keyspace_misses_total{cache="cch_4k2m9x0a7qpe"}[5m])))
)
# Memcached hit ratio over 5 minutes
max(
sum by (role) (rate(memcached_commands_total{cache="cch_4k2m9x0a7qpe", command="get", status="hit"}[5m]))
/ sum by (role) (rate(memcached_commands_total{cache="cch_4k2m9x0a7qpe", command="get"}[5m]))
)Events
A cache’s events list its failovers, switchovers, maintenance, standby changes and upgrades, newest first:
ezgh caches events cch_4k2m9x0a7qpeIn the console, they’re on the cache’s Events tab.