Node Alerting Configuration

Alerting configuration works like a typical logging system where you can filter what messages are logged depending on the configured “level.” For example, in production you may configure your logging level to “Error.” Any logs emitted at a logging level lower than “Error” (Debug, Info, Warning) will not be emitted.

This form provides a way to configure this “logging level.” Actions configured to Children and Dependencies will trigger if their health level breaches the respective Warning, Error, or Critical level.

For example, imagine you configure a node’s Dependencies threshold value to Warning and configure a single Slack action. If any of the node’s dependencies health breach the Warning threshold, a message will be sent to Slack.

If you configure a node’s Dependencies threshold value to Error, and a dependency’s health breaches a Warning threshold, no message will be sent to Slack as Warning is a lower level than Error.

Please refer to What is a Node Relationship? to get more information on how the health of Children and Dependencies are determined.

Children

Children are nodes that are a child to the subject node. Therefore, if any child has a health that breaches a configured level, the respective actions will be triggered.

Dependencies

Dependencies are nodes that this subject node depends on. If any dependency breaches a configured level, the respective actions will be triggered.

Monitors

Configuring monitors at the subject node level allows you to have a single point of configuration for all monitors.

The alerting configuration at the node level will not overwrite the behavior of actions configured to a monitor. Therefore, actions configured on a monitor will be triggered in addition to any actions you configure at the node level.

Again, if you wish to have a single location where you configure alerting actions do not assign Actions to thresholds on the respective monitors. This is especially true for templates. Allow the consumer of the template to configure the actions on template monitors via the node configuration.