- A PagerDuty incident has been created.
- A Datadog alert has been triggered.
- A Zendesk ticket has been created.
Integration | Trigger |
---|---|
PagerDuty | When a PagerDuty Incident is created |
Opsgenie | When an Opsgenie Incident is created |
Splunk On-Call (VictorOps) | When a VictorOps Incident is created |
Datadog | When a Datadog alert is triggered |
Zendesk | When a Zendesk ticket is created (customizable) |
Nobl9 | When an SLO is not satisfied anymore |
Sentry | When a Sentry alert is triggered |
Rootly automatically drops any alerts that are an exact match to another alert’s payload. This helps ensure that you aren’t managing many alerts for the exact same event.
Alert Deduping
Sometimes your monitors will continue to send alerts into Rootly when an issue persists. Rather than creating separate Alerts in Rootly for your engineers to manage and investigate, you’re able to add the subsequent alert to the original as a duplicate event. Engineers can then use this context as they continue to investigate the original alert.
- Navigate to your Alert Source.
- Under the
Events
tab, toggle onCombine duplicate alerts into one alert
. - Set the unique identifier that Rootly will use to map alerts together.
Easily define your unique identifier: You are able to preview your Alert Source’s alerts on the right-hand side. Clicking into an alert will reveal its payload: select one of the purple pills to copy the value’s JSONPath to your clipboard to refer to it as your unique identifier.
