This is the most simple option, allowing for a single service, team or escalation policy to be associated with an alert.
Set the type and id in the webhook url following the default instructions in ‘Step 1’ to indicate on a per webhook basis what type (service, group (team) or escalationPolicy) and the correct id of service, team or escalation policy.
Set the required field ‘notification name’ in Step 2.
Click ‘save’ then ‘I finished this step’ buttons
Note: if type and id are set in the url of Step 1, indicating the type and id can be skipped in Step 2.
Alternatively, the type and id can be set after the call is made, by parsing the response payload from your observability provider. This is a more flexible option allowing multiple types and id’s to be set with a single webhook but requires modification of the observability providers payload.
In your observability provider, update the response payload to include the type (service, group (team) or escalationPolicy) and id (found on each respective objects rootly index page).
Example: {... type: service, type: <service_id>}
In Rootly, set the required field ‘notification name’ in Step 2.
Parse the type and id using jsonpath syntax as indicated in Step 2.
