Systèmes de données
    Elasticsearch logo

    Elasticsearch Suivi

    Surveillez en temps réel l'état de santé du cluster Elasticsearch, les taux d'indexation, l'utilisation du tas JVM et la latence des recherches, sans aucune configuration.

    Pourquoi surveiller ? Elasticsearch?

    Elasticsearch assure les fonctions de recherche, de journalisation et d'analyse pour des milliers d'organisations à travers le monde. La surveillance d'Elasticsearch est essentielle pour maintenir la santé du cluster, optimiser le débit d'indexation, suivre la latence des recherches et éviter l'épuisement du tas de la JVM. L'intégration d'Elasticsearch par Xitoring offre une visibilité approfondie sur tous les aspects de votre 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
    Indicateurs

    Ce que nous moniteur

    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.

    Déclencheurs et alertes

    Configurable déclencheurs d'alerte

    Configurez des déclencheurs personnalisés dans votre tableau de bord pour être averti dès que les indicateurs d{name}s dépassent les seuils que vous avez définis.

    Elasticsearch tableau de bord de configuration des déclencheurs de surveillance

    Cluster Health

    crucial

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

    JVM Heap Usage

    crucial

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

    Indexing Rate

    avertissement

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

    Search Latency

    avertissement

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

    Unassigned Shards

    crucial

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

    Thread Pool Rejections

    avertissement

    Alerts when thread pool queues overflow and start rejecting requests.

    01

    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
    02

    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
    Guide d'installation

    Commencez par procès-verbal

    1

    Install Xitogent on your server

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

    # Get your install command from: xitoring.com → Servers → Add Server curl -s https://xitoring.com/install.sh | sudo bash
    2

    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
    3

    Enable the Elasticsearch integration

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

    xitogent integrate
    4

    Configure alert thresholds (optional)

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

    Souvent a posé des questions

    Commencer à surveiller Elasticsearch aujourd'hui

    Configuration en moins de 60 secondes. Aucune carte bancaire requise. Statistiques complètes dès le premier jour.

    Commencer l'essai gratuit

    Continuez à explorer

    Connexes Intégrations