Kibana

Kibana

This section describes the alerts for the Kibana service.


KibanaProcessDown

Severity Minor
Summary The Kibana process on the {{ $labels.host }} node is down.
Raise condition procstat_running{process_name="kibana"} == 0
Description Raises when Telegraf cannot find a running kibana process, typically indicating that the Kibana process is down on one node. The host label in the raised alert contains the host name of the affected node.
Troubleshooting
  • Verify the Kibana service status on the affected node using systemctl status kibana.
  • Inspect the Kibana service logs using journalctl -xfu kibana.
Tuning Not required

KibanaProcessesDownMinor

Severity Minor
Summary More than 30% of Kibana processes are down.
Raise condition count(procstat_running{process_name="kibana"} == 0) >= count(procstat_running{process_name="kibana"}) * 0.3
Description Raises when Telegraf cannot find running kibana processes on more than 30% of the log hosts.
Troubleshooting
  • Inspect the KibanaProcessDown alerts for the host names of the affected nodes.
  • Verify the Kibana service status on the affected node using systemctl status kibana.
  • Inspect the Kibana service logs using journalctl -xfu kibana.
Tuning Not required

KibanaProcessesDownMajor

Severity Major
Summary More than 60% of Kibana processes are down.
Raise condition count(procstat_running{process_name="kibana"} == 0) >= count(procstat_running{process_name="kibana"}) * 0.6
Description Raises when Telegraf cannot find running kibana processes with on more than 60% of the log hosts.
Troubleshooting
  • Inspect the KibanaProcessDown alerts for the host names of the affected nodes.
  • Verify the Kibana service status on the affected node using systemctl status kibana.
  • Inspect the Kibana service logs using journalctl -xfu kibana.
Tuning Not required

KibanaServiceOutage

Severity Critical
Summary All Kibana processes are down.
Raise condition count(procstat_running{process_name="kibana"} == 0) == count(procstat_running{process_name="kibana"})
Description Raises when Telegraf cannot find running kibana processes on all the log hosts.
Troubleshooting
  • Inspect the KibanaProcessDown alerts for the host names of the affected nodes.
  • Verify the Kibana service status on the affected node using systemctl status kibana.
  • Inspect the Kibana service logs using journalctl -xfu kibana.
Tuning Not required