Skip to content
Osuite Osuite Docs

Notification channels

Notification channels are where Osuite delivers an alert when it fires. Connect a channel once under Settings → General → Notifications, then select it on any alert (see Creating an alert). Osuite supports four channels: Slack, Opsgenie, Zenduty, and PagerDuty.

Every channel receives the same core information when an alert fires:

  • The alert name and severity
  • The state transition (Firing, or Normal when it resolves)
  • The PromQL query and the value that crossed the threshold
  • The time the condition started
  • A link back to the alert in Osuite

The sections below cover how each channel is connected and what the delivered notification looks like.

Slack

Section titled “Slack”

Delivers each alert as a message in a Slack channel.

  1. In Slack, create an incoming webhook for the channel Osuite should post to.
  2. In Settings → General → Notifications, add a Slack channel and paste the webhook URL.
  3. Save the channel. It is now selectable on any alert.

A Slack notification is a message posted to the chosen channel showing the alert name, severity, the query and its current value, and a link back to Osuite. When the alert returns to Normal, Osuite posts a follow-up message marking it resolved.

Opsgenie

Section titled “Opsgenie”

Creates an Opsgenie alert so it enters your on-call routing and escalation.

  1. In Opsgenie, create an API integration and copy its API key.
  2. In Settings → General → Notifications, add an Opsgenie channel and paste the API key.
  3. Save the channel.

When an alert fires, Osuite creates an Opsgenie alert carrying the alert name, severity, and query details; Opsgenie applies your routing and escalation rules. When the Osuite alert returns to Normal, the corresponding Opsgenie alert is closed.

Zenduty

Section titled “Zenduty”

Creates a Zenduty incident routed through your escalation policies.

  1. In Zenduty, add an integration to the relevant service and copy its integration key.
  2. In Settings → General → Notifications, add a Zenduty channel and paste the integration key.
  3. Save the channel.

A firing alert opens a Zenduty incident with the alert name, severity, and query details, which Zenduty routes according to your on-call schedule. The incident is resolved when the Osuite alert returns to Normal.

PagerDuty

Section titled “PagerDuty”

Triggers a PagerDuty incident on a service you choose.

  1. In PagerDuty, add an Events API integration to the target service and copy its integration key.
  2. In Settings → General → Notifications, add a PagerDuty channel and paste the integration key.
  3. Save the channel.

When an alert fires, Osuite triggers a PagerDuty incident with the alert name, severity, and query details, and PagerDuty applies the service’s escalation policy. When the alert returns to Normal, Osuite resolves the incident.

Next steps

Section titled “Next steps”