Integration · Databases
Elasticsearch
Cluster health, shard allocation, ingest throughput.
What gets collected
_cluster/health, _cat/indices, _nodes/stats. Per-index metrics plus circuit breaker triggers.
Requirements
- ✓Elasticsearch 7.x/8.x
- ✓monitor cluster privilege
- ✓read-only user
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
es.cluster.statuses.shards.unassignedes.ingest.throughputes.jvm.heapes.circuit_breaker.tripsSetup steps
- 1A read-only ESuser with the monitor cluster privilege
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
Elasticsearch
Frequently asked questions
- What does Unimoni collect from Elasticsearch?
- Cluster health, shard allocation, ingest throughput. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across Elasticsearch and everything else in one place.
- How long does it take to connect Elasticsearch?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the Elasticsearch integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is Elasticsearch monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.