oliver006/redis_exporter

Prometheus Exporter for Valkey & Redis Metrics. Supports Valkey 9.x, 8.x, 7.x and various Redis versions

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 minute ago
Added to GitGenius on September 18th, 2026
Created on April 28th, 2015
Open Issues & Pull Requests: 12 (+0)
GitHub issues: Enabled
Number of forks: 949
Total Stargazers: 3,695 (+0)
Total Subscribers: 43 (+0)

Repository Insights (GitGenius)

Median issue/PR response: N/A
Mean response time: 14.2 days
90th percentile: 0.0 hours
Tracked items: 89

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Practically every issue opened in the past year has drawn a reply. 93% of issues opened in the past year have since been closed. Three people close 89% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 643 days
Stale 30+ days: 6
Stale 90+ days: 4

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 1
Events in 7 days: 4

Top labels

  • question (62)
  • bug (24)
  • help wanted (9)

Detailed Description

redis_exporter is a Prometheus exporter that collects metrics from Valkey and Redis instances for monitoring and alerting.

The tool solves the problem of integrating Valkey and Redis monitoring into Prometheus-based observability stacks. It exposes Redis metrics in Prometheus format by connecting to Redis or Valkey instances and scraping their INFO command output and other diagnostic data. The exporter can run as a single-instance scraper or as a multi-target exporter that Prometheus queries with different target parameters, allowing a single exporter instance to monitor multiple Redis hosts.

The tool suits teams already using Prometheus who need to monitor Redis or Valkey deployments. It works well in Kubernetes environments where service discovery can automatically identify Redis pods and instances. For Redis Cluster deployments, the exporter includes a cluster discovery endpoint that automatically detects all nodes in the cluster, eliminating the need to manually configure each node. The multi-target mode is useful when you need to monitor many Redis instances with a single exporter, though it currently supports only one password across all targets; separate exporter instances are needed if different targets require different credentials. The exporter supports TLS connections and allows certificate hostname configuration for targets where the certificate name differs from the target address.

Development activity shows consistent maintenance with regular updates addressing compatibility across multiple Valkey versions and Redis variants. The project maintains active engagement with issues and pull requests, indicating responsiveness to user needs and bug reports. Documentation is thorough, covering basic setup, Kubernetes integration patterns, multi-target configurations, and cluster discovery scenarios with concrete examples.