Prometheus-elasticsearch-exporter
A Prometheus exporter that collects and exposes metrics about Elasticsearch and OpenSearch clusters, giving you a standard /metrics endpoint to monitor them…
Platform availability
Available on 1 of 9 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
72/100 Good
- Maintained
- 100last commit 0 days ago
- Popular
- 662,091 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
No GitHub repository data collected yet.
Resources & Compatibility
Requirements not published yet.
First-install notes
- Install & scrape setup Deploy the Elasticsearch Exporter alongside your Prometheus server, configure it with your Elasticsearch or OpenSearch endpoints, and point Prometheus's scrape config at the exporter's /metrics endpoint. The project's deployment guide covers installation methods and configuration for various environments. source
Fetched today - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which port should I expose for the Elasticsearch exporter in Docker?
The Docker examples use port 9114, such as -p 9114:9114 or a docker-compose mapping of 127.0.0.1:9114:9114.
How do I point Prometheus at this exporter?
Configure the exporter with your Elasticsearch or OpenSearch endpoints, then point Prometheus's scrape config at the exporter's /metrics endpoint.
Can a short Prometheus scrape interval hurt Elasticsearch?
The exporter fetches from Elasticsearch on every scrape, so a too-short interval can impose load on ES master nodes, especially with --es.all and --es.indices. You can measure /_nodes/stats and /_all/_stats times or use a dedicated scrape job.
Does the exporter support both Elasticsearch and OpenSearch?
It supports all currently supported versions of Elasticsearch and OpenSearch and attempts to remain compatible with older and diverging versions, though some collectors may only work with one product.
How do I enable cluster settings metrics in newer versions?
Use collector.clustersettings, which was introduced in 1.6.0 and replaced es.cluster_settings. It is false by default.
Answers sourced from deepwiki.com, github.com
Community
No community discussions collected yet.