The Monitoring Console
The Monitoring Console
Section titled “The Monitoring Console”The platform’s own health dashboard — the cluster overview an administrator
reads first to see whether the platform itself is running well. It is the
Monitoring Console app (the cluster_monitoring app), reached from the
app menu, and it answers “is the platform healthy” rather than “is the
customer’s data healthy”.
Overview
Section titled “Overview”The front door: the platform’s core state in one screen.
- Availability — the ratio of available primary shards to all primary shards in the cluster. Watch unusable shards; under load, also watch shards in migration.
- Machine load — load per core (sum of machine loads over sum of cores); above 100% means the service is running under load overall.
- Disk information — cluster disk capacity, watermarks and per-disk distribution.
- Instance deployment — total instances over total machines, i.e. the average instance density per machine.
- Repository information — repos in use, record count and capacity; the guidance is to prefer a reasonable number of repos with sourcetypes for business differentiation rather than many small repos.
- Queries per minute — cluster query load; sustained high volume warrants attention.
- Hotspot threads — where the service’s work is concentrated, useful for governance and diagnosis.
- Repo / shard / disk traffic — per-second write traffic broken down by repo, by shard, and by disk.
- Writes per second — the write load.
The rest of the console
Section titled “The rest of the console”Beyond the overview, the console splits into the surfaces that explain why an overview metric moved:
| surface | what it shows |
|---|---|
| Query Overview / Operator Overview | query traffic and the operators that consume it (exec_overview, query_analysis_* for plans, schedules and tracing) |
| Machine Matrix | per-machine health at a glance |
| Node Load / Node Disk / Node Threads | per-node load, disk and thread breakdowns |
| Data Shards | shard state and distribution |
| Data ILM | index lifecycle state (the retention machinery) |
| Data License | license consumption |
| Collect Overview / Collect Metric | the collection pipeline’s own health (agent metrics and logs) |
| Netflow | netflow collector, data and lag |
| Alert Config / Alert View | the console’s own alerting |
| Node Setting | per-node platform settings |
Everything is the platform monitoring itself: the agents’ metrics and logs
land in the _collector_*/_runner_*-style indexes, the cluster writes to
its shards, and this app reads those back.