Does the integration require authentication?

If your Elasticsearch cluster uses X-Pack security, you can configure credentials in the integration settings. Xitogent supports basic auth and API key authentication.

Will this integration affect Elasticsearch performance?

No. Xitogent uses the lightweight cluster stats and node stats APIs which have negligible impact on cluster performance.

Can I monitor multi-node clusters?

Yes. Install Xitogent on each node for per-node visibility, or on a single node for cluster-wide metrics.

Can I monitor OpenSearch?

The Elasticsearch integration works with OpenSearch 1.x and 2.x since they share compatible APIs.

What Elasticsearch versions are supported?

Xitoring supports Elasticsearch 7.x and 8.x, as well as OpenSearch 1.x and 2.x.

How often are metrics collected?

Metrics are collected at 1-minute intervals by default. This can be adjusted through the Xitoring dashboard or CLI.

Data Systems

Elasticsearch Monitoring

Monitor Elasticsearch cluster health, indexing rates, JVM heap usage, and search latency in real time with zero configuration.

Start Free Trial View Docs

Why monitor Elasticsearch?

Elasticsearch powers search, logging, and analytics for thousands of organizations worldwide. Monitoring Elasticsearch is critical to maintain cluster health, optimize indexing throughput, track search latency, and prevent JVM heap exhaustion. Xitoring's Elasticsearch integration provides deep visibility into every aspect of your cluster.

Auto-discovery via Xitogent — no manual configuration required

Cluster health status and shard allocation tracking

JVM heap usage and garbage collection monitoring

Indexing and search rate performance metrics

Per-node resource utilization breakdown

Pending tasks and circuit breaker monitoring

Works on both Linux and Windows servers

1-minute metric collection intervals

Metrics

What we monitor

Cluster Health

Overall cluster status (green/yellow/red) and active shard count.

JVM Heap Usage

Heap used, committed, and max across all nodes with GC stats.

Indexing Rate

Documents indexed per second across the cluster.

Search Rate

Search queries per second and average search latency.

Shard Count

Active, relocating, initializing, and unassigned shards.

Pending Tasks

Cluster-level pending tasks that can indicate bottlenecks.

CPU Usage

Per-node CPU utilization and OS-level load averages.

Disk Usage

Storage used per node and available disk space.

Thread Pool

Active, queued, and rejected tasks in each thread pool.

Circuit Breakers

Memory estimates and trip counts for request/fielddata/in-flight breakers.

Segment Count

Number of Lucene segments and merge activity.

Fielddata Cache

Fielddata cache size and eviction count.

Triggers & Alerts

Configurable alert triggers

Set up custom triggers in your dashboard to get notified the moment Elasticsearch metrics cross your defined thresholds.

Elasticsearch monitoring trigger configuration dashboard

Cluster Health

critical

Fires when cluster status degrades to yellow or red, indicating shard allocation issues.

JVM Heap Usage

critical

Triggers when JVM heap usage exceeds threshold, risking out-of-memory errors and node instability.

Indexing Rate

warning

Alerts when indexing throughput drops below baseline, indicating ingestion pipeline issues.

Search Latency

warning

Fires when average search latency exceeds threshold, degrading user-facing search quality.

Unassigned Shards

critical

Triggers when shards remain unassigned, leaving data under-replicated and at risk.

Thread Pool Rejections

warning

Alerts when thread pool queues overflow and start rejecting requests.

Importance of Elasticsearch Monitoring

Elasticsearch underpins search functionality, log aggregation, and real-time analytics. Without monitoring, cluster degradation, JVM pressure, and unassigned shards can cascade into search outages and data loss.

Detect cluster health degradation before it impacts search availability
Monitor JVM heap to prevent out-of-memory crashes
Track indexing throughput to ensure data ingestion pipelines stay healthy
Identify unassigned shards that leave data under-replicated
Optimize search latency for user-facing applications

Elasticsearch cluster monitoring dashboard with health and search metrics

Elasticsearch performance dashboard with indexing and node metrics

Why Choose Xitoring

Xitoring delivers enterprise-grade Elasticsearch monitoring with zero-config setup. Our lightweight agent auto-discovers your Elasticsearch nodes, starts collecting metrics in under 60 seconds, and integrates with your existing notification channels.

One-command install — no complex YAML or config files
15+ global monitoring nodes for low-latency checks
Unified dashboard for servers, search clusters, and uptime
Flexible alerting via Slack, PagerDuty, Telegram & more
Historical data retention for capacity planning & audits

Xitoring Elasticsearch cluster monitoring overview

Alert notification and team channels configuration

Before you start

Prerequisites for Elasticsearch

Make sure you've got these in place — most installs are a 60-second job once they are.

Elasticsearch 7.x or 8.x reachable on its REST port (default 9200)
A monitoring user with cluster:monitor privileges if security is enabled
TLS/CA configuration available to Xitogent if HTTPS is required

Setup Guide

Get started in minutes

Install Xitogent on your server

If you haven't already, install the lightweight Xitogent monitoring agent on your server.

curl -s https://xitoring.com/install.sh | sudo bash -s -- --key=YOUR_API_KEY

Verify Elasticsearch API is accessible

Xitogent uses the Elasticsearch REST API to collect metrics. Verify the cluster is reachable:

curl -s http://localhost:9200/_cluster/health | python3 -m json.tool

Enable the Elasticsearch integration

Use the Xitoring dashboard or CLI to enable the Elasticsearch integration.

sudo xitogent integrate

Configure alert thresholds (optional)

Set custom thresholds for cluster health, JVM heap, or indexing rate to get notified when something needs attention.

Verify it's working

Run this command on the server to confirm Xitogent picked up the integration. Fresh metrics will start streaming to your dashboard within ~30 seconds.

sudo xitogent status

Compare

Considering alternatives?

See how Xitoring stacks up against the alternatives for Elasticsearch monitoring — flat pricing, deeper integrations, and one agent that covers your whole stack.