{
  "id": "v1_monitoring",
  "title": "Metrics and alerts for monitoring v1",
  "url": "https://redis.io/docs/latest/operate/rs/8.0/monitoring/v1_monitoring/",
  "summary": "Monitor Redis Software clusters and databases using internal monitoring systems and external monitoring tools.",
  "content": "\n## Current monitoring system (deprecated)\n\nThe current monitoring system, which is deprecated as of Redis Software version 7.22, consists of the following components:\n\n- Internal metrics storage:\n\n    - Metrics are internally aggregated, calculated, and stored for up to one year.\n\n    - This historical data is used to generate trends and performance insights over time.\n\n- [Statistics APIs](https://redis.io/docs/latest/operate/rs/references/rest-api/objects/statistics):\n\n    - This set of RESTful APIs exposes metrics collected at regular intervals from clusters, nodes, databases, shards, and endpoints.\n\n    - These APIs allow customers to retrieve performance and usage statistics directly from the internal storage layer.\n\n- Cluster manager metrics and alerts:\n\n    - The Cluster Manager UI includes [dedicated metrics pages](#cluster-manager-metrics) that display pre-aggregated metrics.\n\n    - [Cluster alerts](#cluster-alerts) are triggered based on thresholds applied to these stored metrics.\n      \n- v1 Prometheus scraping endpoint:\n\n    - Redis Software exposes a legacy `/prometheus_metrics` endpoint to integrate with external observability platforms like [Prometheus and Grafana](https://redis.io/docs/latest/operate/rs/monitoring/get-started).\n\n    - This endpoint fetches data from the internal storage, providing basic monitoring integration.\n\n### Limitations\n\nThe internal monitoring system, while functional, has several limitations that affect scalability and accuracy:\n      \n- **Limited granularity:** Metrics are aggregated before storage, resulting in a loss of fine-grained insights.\n\n- **Stale data:** Stored metrics can lag behind real-time system states, reducing the effectiveness of alerting.\n\n- **Visibility gaps during management operations:** Metrics and statistics may not be available or updated during management tasks, resulting in incomplete monitoring during critical activities.\n\n- **Scalability constraints:** Internal storage and processing introduce performance overhead and are not optimized for large-scale observability pipelines.\n\n- **Limited extensibility:** The system is tightly coupled with internal components, making it difficult to integrate with modern monitoring ecosystems.\n\n### Transition to the metrics stream engine\n\nTo improve monitoring and address current limitations, Redis Software is transitioning to a new observability foundation: the [metrics stream engine](https://redis.io/docs/latest/operate/rs/monitoring/metrics_stream_engine).\n\nThis modern monitoring stack introduces:\n\n- Real-time metrics, exposed directly from the engine without intermediate storage for high-fidelity, low-latency insights.\n\n- Scalable architecture designed for cloud-native observability with lightweight Prometheus collectors.\n\n- Deeper visibility by exposing new types of metrics such as key size distribution, server overall latency histograms, and system internals with per-endpoint resolution.\n\nWe recommend migrating to the metrics stream engine for enhanced accuracy, scalability, and future-proof observability.\n\nIf you are already using the existing scraping endpoint for integration, follow [this guide](https://redis.io/docs/latest/operate/rs/monitoring/metrics_stream_engine/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### Transition cluster manager alerts\n\nAs part of Redis Software's transition to the [new metrics stream engine](https://redis.io/docs/latest/operate/rs/monitoring/metrics_stream_engine), some internal cluster manager alerts were deprecated in favor of external monitoring solutions. See the [alerts transition plan](https://redis.io/docs/latest/operate/rs/monitoring/metrics_stream_engine/alerts-v1-to-v2) for guidance.\n\n## Cluster manager metrics\n\nYou can see the metrics of the cluster in:\n\n- **Cluster \u003e Metrics**\n- **Node \u003e Metrics** for each node\n- **Database \u003e Metrics** for each database, including the shards for that database\n\nThe scale selector at the top of the page allows you to set the X-axis (time) scale of the graph.\n\nTo choose which metrics to display in the two large graphs at the top of the page:\n\n1. Hover over the graph you want to show in a large graph.\n1. Click on the right or left arrow to choose which side to show the graph.\n\nWe recommend that you show two similar metrics in the top graphs so you can compare them side-by-side.\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/flash) databases\n\n## Cluster alerts\n\nIn **Cluster \u003e Alert Settings**, you can enable alerts for node or cluster events, such as high memory usage or throughput.\n\nConfigured alerts are shown:\n\n- As a notification on the status icon (  ) for the node and cluster\n- In the **log**\n- In email notifications, if you configure [email alerts](#send-alerts-by-email)\n\n\nIf you enable alerts for \"Node joined\" or \"Node removed\" actions,\nyou must also enable \"Receive email alerts\" so that the notifications are sent.\n\n\nTo enable alerts for a cluster:\n\n1. In **Cluster \u003e Alert Settings**, click **Edit**. \n1. Select the alerts that you want to show for the cluster and click **Save**.\n\n## Database alerts\n\nFor each database, you can enable alerts for database events, such as high memory usage or throughput.\n\nConfigured alerts are shown:\n\n- As a notification on the status icon (  ) for the database\n- In the **log**\n- In emails, if you configure [email alerts](#send-alerts-by-email)\n\nTo enable alerts for a database:\n\n1. In **Configuration** for the database, click **Edit**.\n1. Select the **Alerts** section to open it.\n1. Select the alerts that you want to show for the database and click **Save**.\n\n## Send alerts by email\n\nTo send cluster and database alerts by email:\n\n1. In **Cluster \u003e Alert Settings**, click **Edit**.\n1. Select **Set an email** to configure the [email server settings](https://redis.io/docs/latest/operate/rs/clusters/configure/cluster-settings#configuring-email-server-settings).\n1. In **Configuration** for the database, click **Edit**.\n1. Select the **Alerts** section to open it.\n1. Select **Receive email alerts** and click **Save**.\n1. In **Access Control**, select the [database and cluster alerts](https://redis.io/docs/latest/operate/rs/security/access-control/manage-users) that you want each user to receive.\n",
  "tags": ["docs","operate","rs","kubernetes"],
  "last_updated": "2026-07-23T11:57:56-05:00"
}