Project: Netdata (Observability and Analysis / Observability)
File: netdata_agent_alarms.md

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/collectors/python.d.plugin/alarms/README.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/python.d.plugin/alarms/metadata.yaml" sidebar_label: "Netdata Agent alarms" learn_status: "Published" learnrelpath: "Collecting Metrics/Other" most_popular: False message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE" endmeta--> Plugin: python.d.plugin Module: alarms <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> This collector creates an 'Alarms' menu with one line plot of `alarms.status`. Alarm status is read from the Netdata agent rest api . This collector is supported on all platforms. This collector supports collecting metrics from multiple instances of this integration, including remote instances. It discovers instances of Netdata running on localhost, and gathers metrics from `http://127.0.0.1:19999/api/v1/alarms?all`. `CLEAR` status is mapped to `0`, `WARNING` to `1` and `CRITICAL` to `2`. Also, by default all alarms produced will be monitored. The default configuration for this integration does not impose any limits on data collection. The default configuration for this integration is not expected to impose a significant performance impact on the system. Metrics grouped by scope. The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels. These metrics refer to the entire monitored application. This scope has no labels. Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | alarms.status | a dimension per alarm representing the latest status of the alarm. | status | | alarms.values | a dimension per alarm representing the latest collected value of the alarm. | value | There are no alerts configured by default for this integration. No action required. The configuration file name for this integration is `python.d/alarms.conf`. You can edit the configuration file using the `edit-config` script from the Netdata . ```bash cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata sudo ./edit-config python.d/alarms.conf ``` There are 2 sections: Global variables One or more JOBS that can define multiple different instances to monitor. The following options can be defined globally: priority, penalty, autodetectionretry, updateevery, but can also be defined per JOB to override the global values. Additionally, the following collapsed table contains all the options that can be configured inside a JOB definition. Every configuration JOB starts with a `job_name` value which will appear in the dashboard, unless a `name` parameter is specified. <details><summary>Config options</summary> | Name | Description | Default | Required | |:-|:--|:-|:--:| | url | Netdata agent alarms endpoint to collect from. Can be local or remote so long as reachable by agent. | http://127.0.0.1:19999/api/v1/alarms?all | yes | | status_map | Mapping of alarm status to integer number that will be the metric value

| {"CLEAR": 0, "WARNING": 1, "CRITICAL": 2} | yes | | collectalarmvalues | set to true to include a chart with calculated alarm values over time. | no | yes | | alarmstatuschart_type | define the type of chart for plotting status over time e.g. 'line' or 'stacked'. | line | yes | | alarmcontainswords | A "," separated list of words you want to filter alarm names for. For example 'cpu,load' would filter for only alarms with "cpu" or "load" in alarm name. Default includes all. | | yes | | alarmexcludeswords | A "," separated list of words you want to exclude based on alarm name. For example 'cpu,load' would exclude all alarms with "cpu" or "load" in alarm name. Default excludes None. | | yes | | update_every | Sets the default data collection frequency. | 10 | no | | priority | Controls the order of charts at the netdata dashboard. | 60000 | no | | autodetection_retry | Sets the job re-check interval in seconds. | 0 | no | | penalty | Indicates whether to apply penalty to update_every in case of failures. | yes | no | | name | Job name. This value will overwrite the `job_name` value. JOBS with the same name are mutually exclusive. Only one of them will be allowed running at any time. This allows autodetection to try several alternatives and pick the one that works. | | no | </details> A basic example configuration. ```yaml jobs: url: 'http://127.0.0.1:19999/api/v1/alarms?all' ``` An advanced example configuration with multiple jobs collecting different subsets of alarms for plotting on different charts. "ML" job will collect status and values for all alarms with "ml_" in the name. Default job will collect status for all other alarms. <details><summary>Config</summary> ```yaml ML: update_every: 5 url: 'http://127.0.0.1:19999/api/v1/alarms?all' status_map: CLEAR: 0 WARNING: 1 CRITICAL: 2 collectalarmvalues: true alarmstatuschart_type: 'stacked' alarmcontainswords: 'ml_' Default: update_every: 5 url: 'http://127.0.0.1:19999/api/v1/alarms?all' status_map: CLEAR: 0 WARNING: 1 CRITICAL: 2 collectalarmvalues: false alarmstatuschart_type: 'stacked' alarmexcludeswords: 'ml_' ``` </details> To troubleshoot issues with the `alarms` collector, run the `python.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. Navigate to the `plugins.d` directory, usually at `/usr/libexec/netdata/plugins.d/`. If that's not the case on your system, open `netdata.conf` and look for the `plugins` setting under `[directories]`. ```bash cd /usr/libexec/netdata/plugins.d/ ``` Switch to the `netdata` user. ```bash sudo -u netdata -s ``` Run the `python.d.plugin` to debug the collector: ```bash ./python.d.plugin alarms debug trace ```