Redis Enterprise OpenTelemetry Assets

Redis Enterprise is a commercial, enterprise-grade Redis platform that provides clustered, highly available in-memory databases with sub-millisecond latency, automatic failover, and multi-tenancy across distributed nodes.

These assets provide dashboards, alert rules, and SLO templates for monitoring Redis Enterprise clusters using metrics collected by the OpenTelemetry Collector Prometheus receiver from the Redis Enterprise v2 metrics endpoint, covering database performance, node infrastructure health, proxy and listener activity, shard-level diagnostics, and operational alerting.

The Redis Enterprise OpenTelemetry assets have been tested with the OpenTelemetry Collector Contrib Prometheus receiver v0.145.0 scraping the Redis Enterprise v2 metrics endpoint (port 8070).

You need Elasticsearch for storing and searching your data and Kibana for visualizing and managing it. You can use our hosted Elasticsearch Service on Elastic Cloud, which is recommended, or self-manage the Elastic Stack on your own hardware.

The Redis Enterprise cluster must expose its v2 metrics endpoint. This is enabled by default on port 8070 on each cluster node. Verify that the endpoint is accessible from the host running the OpenTelemetry Collector:

curl -sk https://<REDIS_ENTERPRISE_HOST>:8070/v2
		

You should receive a Prometheus-formatted metrics response. If the endpoint is not accessible, check your network configuration and ensure TLS certificates are valid. The Prometheus receiver authenticates using the cluster credentials when TLS is enabled.

You can use the OpenTelemetry Collector or the Elastic Distribution of OpenTelemetry Collector (EDOT Collector) to collect Redis Enterprise metrics.

Placeholders used in the configuration below:

• <REDIS_ENTERPRISE_HOST> — Hostname or IP address of a Redis Enterprise cluster node (e.g., redis-cluster-1.example.com).
• <ES_ENDPOINT> — Your Elasticsearch endpoint URL (e.g., https://my-deployment.es.us-central1.gcp.cloud.es.io:443).
• ${env:ES_API_KEY} — Elasticsearch API key, set via the ES_API_KEY environment variable.

receivers:
  prometheus/redisenterprise:
    config:
      scrape_configs:
        - job_name: redisenterprise
          scrape_interval: 30s
          scheme: https
          tls_config:
            insecure_skip_verify: true
          static_configs:
            - targets:
                - "<REDIS_ENTERPRISE_HOST>:8070"
          metrics_path: /v2

processors:
  resource:
    attributes:
      - key: data_stream.dataset
        value: redisenterprise
        action: upsert

exporters:
  elasticsearch/otel:
    endpoints:
      - "<ES_ENDPOINT>"
    api_key: ${env:ES_API_KEY}
    mapping:
      mode: otel
    logs_dynamic_index:
      enabled: true
    metrics_dynamic_index:
      enabled: true

service:
  pipelines:
    metrics:
      receivers:
        - prometheus/redisenterprise
      processors:
        - resource
      exporters:
        - elasticsearch/otel
		

The Redis Enterprise v2 metrics endpoint exposes Prometheus-formatted metrics covering all levels of the cluster hierarchy: cluster, node, database (BDB), listener/endpoint, DMC proxy, and shard (Redis process). These are collected using the Prometheus receiver from the OpenTelemetry Collector Contrib repository. Refer to the Redis Enterprise metrics documentation for details on available metrics and their definitions.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.

← →

×

×

×

×

×