Elasticsearch 監視
設定不要で、Elasticsearch クラスタの健全性、インデックス作成レート、JVM ヒープ使用量、検索レイテンシをリアルタイムで監視できます。
なぜ監視するのか Elasticsearch?
Elasticsearchは、世界中の何千もの組織において、検索、ロギング、分析機能を支えています。Elasticsearchの監視は、クラスタの状態を維持し、インデックス作成のスループットを最適化し、検索のレイテンシを追跡し、JVMヒープの枯渇を防ぐために不可欠です。XitoringのElasticsearch統合機能により、クラスタのあらゆる側面を詳細に把握することができます。
私たちが モニター
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.
設定可能 アラートのトリガー
ダッシュボードでカスタムトリガーを設定し、Elasticsearchのメトリクスが定義した閾値を超えた瞬間に通知を受け取れるようにします。
Cluster Health
重要なFires when cluster status degrades to yellow or red, indicating shard allocation issues.
JVM Heap Usage
重要なTriggers when JVM heap usage exceeds threshold, risking out-of-memory errors and node instability.
Indexing Rate
警告Alerts when indexing throughput drops below baseline, indicating ingestion pipeline issues.
Search Latency
警告Fires when average search latency exceeds threshold, degrading user-facing search quality.
Unassigned Shards
重要なTriggers when shards remain unassigned, leaving data under-replicated and at risk.
Thread Pool Rejections
警告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
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
はじめに 議事録
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 bashVerify 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.toolEnable the Elasticsearch integration
Use the Xitoring dashboard or CLI to enable the Elasticsearch integration.
xitogent integrateConfigure alert thresholds (optional)
Set custom thresholds for cluster health, JVM heap, or indexing rate to get notified when something needs attention.
頻繁に 質問をした
探検を続けよう
