Alarms

This collector creates an 'Alarms' menu with one line plot showing alarm states over time. Alarm states are mapped to integer values according to the below default mapping. Any alarm status types not in this mapping will be ignored (Note: This mapping can be changed by editing the status_map in the alarms.conf file). If you would like to learn more about the different alarm statuses check out the docs here.

{
'CLEAR': 0,
'WARNING': 1,
'CRITICAL': 2
}

Charts#

Below is an example of the chart produced when running stress-ng --all 2 for a few minutes. You can see the various warning and critical alarms raised.

alarms collector

Configuration#

Enable the collector and restart Netdata.

cd /etc/netdata/
sudo ./edit-config python.d.conf
# Set `alarms: no` to `alarms: yes`
sudo systemctl restart netdata

If needed, edit the python.d/alarms.conf configuration file using edit-config from the your agent's config directory, which is usually at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory, if different
sudo ./edit-config python.d/alarms.conf

The alarms specific part of the alarms.conf file should look like this:

# what url to pull data from
local:
url: 'http://127.0.0.1:19999/api/v1/alarms?all'
# define how to map alarm status to numbers for the chart
status_map:
CLEAR: 0
WARNING: 1
CRITICAL: 2

It will default to pulling all alarms at each time step from the Netdata rest api at http://127.0.0.1:19999/api/v1/alarms?all

Last updated on

Monitor everything in real time – for free

Troubleshoot slowdowns and anomalies in your infrastructure with thousands of per-second metrics, meaningful visualizations, and insightful health alarms with zero configuration.

Get Netdata