Using Predefined Variables

In the Custom Payload of a Generic Webhook, you can use a set of predefined tags. These tags are automatically populated using the {{ }} syntax.

Below is a list of the available tags:

• summary - The monitor title from the issue details

• description - The monitor description from the issue details - It can contain by itself a set of tags and structured json that are based on the monitor definitions

• monitor_name - The actual name of the monitor

• monitor_id - An internal unique id of the monitor as assigned by groundcover in the database

• fingerprint - A unique id for the specific issue of the monitor that fired with a set of specific labels. This is a good tag to use for deduping incidents

• severity - The monitor severity

• value - The actual monitor value that triggered the monitor

• threshold - The threshold that was set in the monitor for deciding whether to trigger it

• urls.issue - Url to the issue generated from the firing monitor, for further investigation

• urls.monitor - Url to the firing monitor definitions, for further investigation

• urls.silence - Url for directly silencing the monitor that fired

• urls.notification_route - Url to the notification route involved in routing the firing monitor

In addition, any label that is added in any monitor can be used with the annotation labels.<label>. This includes both custom labels and group by labels.

For example: {{labels.traceID}}