{
  "schema_version": 2,
  "id": "operate/rs/references/metrics",
  "title": "Real-time metrics",
  "url": "https://redis.io/docs/latest/operate/rs/7.8/references/metrics/",
  "summary": "Documents the metrics that are tracked with Redis Enterprise Software.",
  "content": "\n## Cluster manager metrics\n\nIn the Redis Enterprise Cluster Manager UI, you can see real-time performance metrics for clusters, nodes, databases, and shards, and configure alerts that send notifications based on alert parameters. Select the **Metrics** tab to view the metrics for each component. For more information, see [Monitoring with metrics and alerts](https://redis.io/docs/latest/operate/rs/monitoring).\n\nSee the following topics for metrics definitions:\n- [Database operations](https://redis.io/docs/latest/operate/rs/references/metrics/database-operations) for database metrics\n- [Resource usage](https://redis.io/docs/latest/operate/rs/references/metrics/resource-usage) for resource and database usage metrics\n- [Auto Tiering](https://redis.io/docs/latest/operate/rs/references/metrics/auto-tiering) for additional metrics for [Auto Tiering ](https://redis.io/docs/latest/operate/rs/databases/auto-tiering) databases\n\n## Prometheus metrics\n\nTo collect and display metrics data from your databases and other cluster components,\nyou can connect your [Prometheus](https://prometheus.io/) and [Grafana](https://grafana.com/) server to your Redis Enterprise Software cluster. We recommend you use Prometheus and Grafana to view metrics history and trends.\n\nSee [Prometheus integration](https://redis.io/docs/latest/operate/rs/monitoring/prometheus_and_grafana) to learn how to connect Prometheus and Grafana to your Redis Enterprise database.\n\nRedis Enterprise version 7.8.2 introduces a preview of the new metrics stream engine that exposes the v2  Prometheus scraping endpoint at `https://\u003cIP\u003e:8070/v2`.\nThis new engine exports all time-series metrics to external monitoring tools such as Grafana, DataDog, NewRelic, and Dynatrace using Prometheus.\n\nThe new engine enables real-time monitoring, including full monitoring during maintenance operations, providing full visibility into performance during events such as shards' failovers and scaling operations.\n\nFor a list of available metrics, see the following references:\n\n- [Prometheus metrics v1](https://redis.io/docs/latest/operate/rs/references/metrics/prometheus-metrics-v1)\n\n- [Prometheus metrics v2 preview](https://redis.io/docs/latest/operate/rs/references/metrics/prometheus-metrics-v2)\n\nIf you are already using the existing scraping endpoint for integration, follow [this guide](https://redis.io/docs/latest/operate/rs/references/metrics/prometheus-metrics-v1-to-v2) to transition and try the new engine. It is possible to scrape both existing and new endpoints simultaneously, allowing advanced dashboard preparation and a smooth transition.\n\n## Limitations\n\n### Shard limit\n\nMetrics information is not shown for clusters with more than 128 shards. For large clusters, we recommend you use [Prometheus and Grafana](https://redis.io/docs/latest/operate/rs/monitoring/prometheus_and_grafana) to view metrics.\n\n### Metrics not shown during shard migration\n\nThe following metrics are not measured during [shard migration](https://redis.io/docs/latest/operate/rs/databases/configure/replica-ha) when using the [internal monitoring systems](https://redis.io/docs/latest/operate/rs/monitoring/v1_monitoring). If you view these metrics while resharding, the graph will be blank.\n\n- [Evicted objects/sec](https://redis.io/docs/latest/operate/rs/references/metrics/database-operations#evicted-objectssec)\n- [Expired objects/sec](https://redis.io/docs/latest/operate/rs/references/metrics/database-operations#expired-objectssec)\n- [Read misses/sec](https://redis.io/docs/latest/operate/rs/references/metrics/database-operations#read-missessec)\n- [Write misses/sec](https://redis.io/docs/latest/operate/rs/references/metrics/database-operations#write-missessec)\n- [Total keys](https://redis.io/docs/latest/operate/rs/references/metrics/database-operations#total-keys)\n- [Incoming traffic](https://redis.io/docs/latest/operate/rs/references/metrics/resource-usage#incoming-traffic)\n- [Outgoing traffic](https://redis.io/docs/latest/operate/rs/references/metrics/resource-usage#outgoing-traffic)\n- [Used memory](https://redis.io/docs/latest/operate/rs/references/metrics/resource-usage#used-memory)\n\nThis limitation does not apply to the new [metrics stream engine](https://redis.io/docs/latest/operate/rs/monitoring/metrics_stream_engine).\n",
  "tags": ["docs","operate","rs","rc"],
  "last_updated": "2026-10-21T09:46:20-07:00",
  "children": [{"id":"operate/rs/references/metrics/prometheus-metrics-v1","summary":"V1 metrics available to Prometheus.","title":"Prometheus metrics v1","url":"https://redis.io/docs/latest/operate/rs/7.8/references/metrics/prometheus-metrics-v1/"},{"id":"operate/rs/references/metrics/prometheus-metrics-v1-to-v2","summary":"Transition from v1 metrics to v2 PromQL equivalents.","title":"Transition from Prometheus v1 to Prometheus v2","url":"https://redis.io/docs/latest/operate/rs/7.8/references/metrics/prometheus-metrics-v1-to-v2/"},{"id":"operate/rs/references/metrics/prometheus-metrics-v2","summary":"V2 metrics available to Prometheus as of Redis Enterprise Software version 7.8.2.","title":"Prometheus metrics v2 preview","url":"https://redis.io/docs/latest/operate/rs/7.8/references/metrics/prometheus-metrics-v2/"},{"id":"operate/rs/references/metrics/auto-tiering","summary":"","title":"Auto Tiering Metrics","url":"https://redis.io/docs/latest/operate/rs/7.8/references/metrics/auto-tiering/"},{"id":"operate/rs/references/metrics/database-operations","summary":"","title":"Database operations metrics","url":"https://redis.io/docs/latest/operate/rs/7.8/references/metrics/database-operations/"},{"id":"operate/rs/references/metrics/resource-usage","summary":"","title":"Resource usage metrics","url":"https://redis.io/docs/latest/operate/rs/7.8/references/metrics/resource-usage/"}]
}