Slack and PagerDuty integrations
Route alerts to approved destinations with stable incident correlation and visible delivery failures.
Notification integrations deliver Infra alert events to Slack channels or PagerDuty services. They use configured routes and consumer credentials rather than a member's interactive session.
Connect a destination
Open Observe → Destinations, choose the integration, and complete the approved provider authorization. Select the Slack workspace and channel or PagerDuty service, then send a test notification.
The test checks the current delivery path. It does not establish that future incidents will match the route. Preview severity, project, owner, and label filters before enabling production routing.
Group and correlate
Routes assign a stable correlation identity to an alert instance. Repeated firing updates can update the existing provider incident rather than creating a new one. A resolution is sent only for the corresponding correlated instance.
A delayed or repeated delivery must not close a newer incident with another identity. Keep the provider mapping and original event IDs available when replaying failed attempts.
Acknowledgement
An acknowledgement in Slack or PagerDuty is reflected in Infra only when the bidirectional callback integration is configured and authenticated. Otherwise the external acknowledgement remains external.
Acknowledgement does not change node health, metric observations, or storage redundancy. Application and infrastructure recovery remain separate actions.
Failures and rotation
Inspect provider status, authorization scope, revoked tokens, rate limits, and channel or service existence. An alert can remain firing while every delivery attempt fails. Use an independent critical notification path when necessary.
Rotate credentials with overlap and verify the consumer's active revision before revoking the old provider credential. Disabling a destination stops new attempts; it does not resolve or delete incidents already created in the external service.
See alert routing, Webhook API, and external secrets.