On-call Assistant

Cortex’s On-call Assistant leverages the PagerDuty integration to automatically surface the most vital information about entity health and metadata when an incident is triggered. On-call Assistant notifies the user(s) responsible for an incident via Slack, including information about the affected entity, 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.

Notifications

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 entity information that is already in Cortex directly from the Slack notification to quickly resolve issues. On-call Assistant provides a direct link to view the alert in PagerDuty, so you can also quickly access the incident from its source.

View runbooks and other links

View dependencies

Enabling On-call Assistant

You can toggle On-call Assistant on or off from the PagerDuty Settings page.

API key with Write permissions

If you added PagerDuty API key with Write permissions, 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.

API key with Read-only permissions

If you added PagerDuty API key with Read-only permissions, you'll need to take some additional steps 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 return to this process later by clicking Configure webhook.