Notification channel guides

Configure destinations under Integrations → Channels. Save the channel, use Send test, confirm the message at the provider, then select it in routing or an escalation policy. A successful test proves provider acceptance, not human receipt; Notification delivery log records later attempts.

Direct and ChatOps channels

Paging and push

Ticketing, automation, and fan-out

Ticketing channels create work items; closing one does not resolve the HowlOps incident unless its guide explicitly says otherwise. Routing precedence, filters, quiet hours, and recovery behavior are explained in Notifications and Alert and incident flow.

Common troubleshooting

1. Send a test from the exact channel card.
2. Inspect Notification delivery log, including provider status and the redacted error.
3. Confirm the channel is enabled and selected by the winning route or escalation step.
4. Check event filters, quiet hours, provider permissions, quotas, and destination membership.
5. To rotate a credential, create its replacement, update HowlOps, test, and only then revoke the old one.