Notification Channels

Notification channels define where alert notifications are sent when an escalation policy triggers. Channels are configured once and reused across multiple escalation policies and levels. The Notification Channels page at /monitoring/notifications provides setup forms for each channel type.

Channel Type Setup

Slack

Slack notifications are delivered via an incoming webhook or an OAuth app installation:

• Webhook URL: Paste a Slack incoming webhook URL (format: https://hooks.slack.com/services/...)
• Channel Name: The Slack channel where notifications are posted (e.g., #ops-alerts). Must match the channel configured in the webhook app.
• Message Format: Alert messages include severity emoji, rule name, metric value vs. threshold, and a link to the Quper alert detail page.

Email

• Recipients: Comma-separated list of email addresses. Supports distribution lists.
• Subject Template: Customizable subject line. Available variables: {{severity}}, {{rule_name}}, {{metric_value}}.
• Delivery: Sent via SendGrid API or SMTP depending on tenant configuration in Settings.

PagerDuty

• Integration Key: The PagerDuty service integration key (Events API v2). Create a new integration from your PagerDuty service page and copy the Routing Key.
• Severity Mapping: Maps Quper severity levels to PagerDuty severities. Default: critical → critical, warning → warning, info → info.
• Acknowledgments in PagerDuty are synced back to Quper via a PagerDuty webhook configured in Settings.

Webhook (Custom HTTP)

• URL: The HTTP endpoint that receives the alert payload. Must be publicly reachable from the Quper API server.
• Custom Headers: Key-value pairs for authentication headers (e.g., Authorization: Bearer ... for internal services).
• Method: POST or PUT.
• Payload is a JSON object containing: alert_id, rule_name, severity, metric_value, threshold_value, fired_at.

Testing a Channel

Every channel card includes a Send Test button. Clicking it dispatches a test notification payload to verify the configuration is correct before the channel is used in a live escalation. The UI shows a success confirmation or the error returned by the downstream service.

Channel Management