{{ incident.service }}
option from this dropdown.
{{ incident.service }}
, instead of {{ incident.services }}
(as you see referenced everywhere else in Rootly) is due to the limitation that one Rootly incident can only be linked to one PagerDuty incident.In the scenario where a Rootly incident has been marked with multiple services, Rootly will only page the first service in the array of services.service
. This field is only used if you’d like the page to follow a different escalation policy from the default that’s associated with the service.
service
. This field is only used if you’d like to page a specific user from the default on-call rotation associated with the service.
{{ incident.service }}
option from this dropdown.
The value set in this field will override the escalation policy & schedule selected below.
service
. This field is only used if you’d like the role assignment to follow a different escalation policy from the default that’s associated with the service.
service
. This field is only used if you’d like to assign from a specific on-call rotation that’s different from the default on-call rotation associated with the service.
{{ incident.service }}
option from this dropdown.
The value set in this field will override the escalation policy & schedule selected below.
{{ incident.slack_channel_id }}
or {{ parent_incident.slack_channel_id }}
to specify your incident channel or the parent incident channel, respectively.
service
. This field is only used if you’d like to invite a specific on-call rotation that’s different from the default on-call rotation associated with the service.
{{ incident.pagerduty\_incident\_id }}
to reference the existing PagerDuty incident that is linked to the Rootly incident.
{{ incident.title }}
if you want the PagerDuty incident title to match the title of your Rootly incident.
{{ incident.pagerduty_incident_id }}
to reference the existing PagerDuty incident that is linked to the Rootly incident.
{{ incident.events | where: 'kind', 'event' | last | get: 'event' }}
to log the latest event that happened to the Rootly incident.