This page explains how to create and configure a custom webhook notifier.
application/json
together with any other headers you specify.
To create a custom webhook notifier, follow these steps:
.Action
has value Open
when the notification corresponds to a match monitor matching or a threshold monitor triggering, and has value Closed
when the notification corresponds to a threshold monitor resolving..MonitorID
is the unique identifier for the monitor associated with the notification..Body
is the message body associated with the notification. When the notification corresponds to a match monitor, this is the matching event data. When the notification corresponds to a threshold monitor, this provides information about the value that gave rise to the monitor triggering or resolving..Description
is the description of the monitor associated with the notification..QueryEndTime
is the end time applied in the monitor query that gave rise to the notification..QueryStartTime
is the start time applied in the monitor query that gave rise to the notification..Timestamp
is the time the notification was generated..Title
is the name of the monitor associated with the notification..Value
is the value that gave rise to the monitor triggering or resolving. It’s only applicable if the notification corresponds to a threshold monitor..MatchedEvent
is a JSON object that represents the event that matched the criteria of the monitor. It’s only applicable if the notification corresponds to a match monitor..GroupKeys
and .GroupValues
are JSON arrays that contain the keys and the values returned by the group-by attributes of your query. They are only applicable if the APL query of the monitor groups by a non-time field.
You can fully customize the content of the webhook to match the requirements of your environment.deduplication_key
.