How notifications work in Grafana Cloud Asserts

This topic describes what happens when you create a notification in Asserts.

Intention

Asserts uses ALERTS to generate assertions. In most cases, you don’t want the system to notify you when each assertion fires as this can create quite a bit of noise. To reduce the noise, you can you can create notifications that let you select various filters for the assertions you need to be notified on.

What happens when you create a notification

When you create a notification, Asserts generates an alerting rule with specific labels that can be consumed by an Alertmanager template. These rules all have the alertname called NOTIFICATION_ALERTS. The following table shows the special labels and values so that you can identify and route the notification to facilitate linking back to the Asserts RCA workbench:

Label	Value	Description
`alertname`	`NOTIFICATION_ALERTS`	All notification alerts have this name.
`source_alertname`	`<ORIGINAL ALERTNAME>`	The original or source `alertname` label value.
`asserts_assertion_name`		The assertion name that’s associated with the alert. This value is used to link back to RCA workbench, for example, `NETWORK:RX_BYTES::ResourceRateAnomaly`.
`asserts_notification_rule_name`	`<NOTIFICATION RULE NAME>`	The name of the notification rule when created in the Grafana Cloud user interface. This can be different from the `alertname` label if desired.