Notifications
Operyn notifies teams when incidents are detected and as remediation workflows progress. Notifications are delivered through channels configured in the Dashboard.
Notification Flow
When an incident is created or updated, the Notification Service formats an event payload and dispatches it to the configured destinations. Each event includes incident context such as service, severity, timestamps, and a direct link to the incident in the Dashboard.
Supported Channels
Slack
Slack messages are sent to the configured channel using an incoming webhook. Slack notifications provide real-time incident awareness with color-coded severity levels.
Discord
Discord notifications are sent as rich embeds with incident severity, description, affected services, and a direct link to the Dashboard.
Jira
Jira integration automatically creates tickets for HIGH and CRITICAL severity incidents. Credentials are encrypted at rest, and subsequent incident updates add comments to the existing ticket.
Webhooks
Generic webhooks POST a JSON payload to any HTTP(S) endpoint. This enables integration with internal dashboards, paging systems (PagerDuty, Opsgenie), ticketing systems, or custom automation workflows.
⚠️ Coming Soon — Email notifications via SMTP are currently in development.
Delivery and Reliability
Delivery is designed to be resilient: failures are retried according to the service's retry policy. If a destination is misconfigured, notifications degrade gracefully for other channels.
Configuring Notifications
Configure notification channels in the Dashboard at Console → Integrations.
See the Notification Channels Setup Guide for detailed step-by-step instructions for Slack, Discord, Jira, PagerDuty, Datadog, Grafana, and webhooks.
Testing
Each channel supports a Test button that sends a synthetic "Test Incident" to verify connectivity before enabling the channel for production use.