Notification channels

A notification channel is a destination for alerts. You configure channels once on the Notification Channels page (under Alerts), then attach them to rules via each rule's escalation chain. When a rule fires — or resolves — every channel on its chain receives a notification.

Channel types

Hexcovery delivers to two kinds of destination:

• Webhooks — an HTTP POST to a URL you provide. This covers:
  • Slack — post into a channel via a Slack incoming webhook.
  • PagerDuty — open and resolve incidents.
  • Discord — post into a channel via a Discord webhook.
  • Any HTTP endpoint — your own service, an automation, a gateway. If it accepts an HTTP POST, it can receive alerts.
• Email — deliver the alert to one or more email addresses.

The standard JSON payload

Webhook channels receive a standard JSON payload describing the alert. The same structure is sent for every webhook channel, so one receiver can handle alerts from any rule — including a firing notification and the matching resolved notification, which carry the rule's current state. This makes it straightforward to forward alerts into a custom integration or to route them yourself.

Testing a webhook

Point a channel at a request-inspection endpoint (or your own service with logging) and trigger a rule to see the exact payload your receiver will get before wiring it into production handling.

Escalation

A rule's escalation chain is an ordered list of channels. When the rule fires, Hexcovery walks the chain and notifies its channels; when the rule resolves, the chain is notified of the resolution.

Notifications are de-duplicated — you are notified on a state change (OK → FIRING, FIRING → OK), not repeatedly on every evaluation while a condition continues to hold. So a long-running incident produces one firing notification and one resolved notification per channel, not a stream of identical pages.

Read next

• Alert rules — attach channels to a rule's escalation chain.
• Incidents — what gets recorded each time a rule fires.