Cortex’s On-call Assistant leverages the PagerDuty integration to automatically surface the most vital information about your service health and metadata when an incident is triggered. On-call Assistant notifies the user responsible for an incident via Slack, including information about the affected service, recent deployments, ownership, and links to get more details, including dependencies, runbooks, and logs.
On-call Assistant helps users respond to incidents in real time, simplifying the incident response process and helping to reduce MTTR. It can also drive adoption and engagement through links to the catalogs and Scorecards.
When an incident is triggered in PagerDuty, On-call Assistant will notify relevant users via Slack. This alert will include information about the affected entity, deploy details, and ownership information so an on-call team member can reach out to other relevant parties about the incident.
Developers can access service information that is already in Cortex directly from the Slack notification to quickly resolve issues.On-call Assistant also provides a direct link to View alert in PagerDuty, so you can also quickly access the incident from its source.
View runbooks and other links
Enabling On-call Assistant
To enable on-call Assistant, navigate to Settings and then scroll down to Integrations -> PagerDuty.
Full Access PagerDuty API key
If your PagerDuty API key is “Full Access”, toggling Enable On-Call Assistant on will create a webhook subscription in PagerDuty, allowing Cortex to receive events when incidents are triggered, escalated, or unacknowledged.
Read-only PagerDuty API key
If you have a “Read-only” PagerDuty API key, there are some additional steps that you will need to complete in PagerDuty and Cortex to configure the webhook subscription. Toggling Enable On-Call Assistant on will guide you through the setup, and you can always get back to this process later by clicking Configure webhook.