Atatus provides a wide range of notification channels so you can receive alert notifications wherever your team works. Channels are attached to alert policies — when an incident is created, every channel linked to the policy receives a notification.

Communication

Incident management

Issue tracking

Custom

Channel settings

Each channel type requires specific configuration fields:

Channel Type Required Settings
Email recipient (email address)
Slack url (webhook URL)
Microsoft Teams url (webhook URL)
Google Chat url (webhook URL)
PagerDuty routing_key or serviceKey
OpsGenie apiKey, optional: recipients, tags, teams
VictorOps apiKey, routingKey
Webhook url
Jira url, username, password or apiKey, projectKey, issueType
ServiceNow instanceName, userName, password
HipChat apiToken, roomId
Campfire subdomain, apiToken, roomId
Flowdock apiToken
BigPanda appKey, token
Twilio accountSid, authToken, fromPhoneNo, toPhoneNo

Testing channels

You can verify that a channel is configured correctly by sending a test notification. Navigate to Alerting > Notification Channels, select the channel, and click the test button. You can also test programmatically via the API endpoint POST /channels/testmessage.

You can choose notification channels from Alerting > Notification Channels. Or, you can add the channels when creating a new alert policy.

At minimum, configure one email channel for a permanent record and one real-time channel like Slack or Microsoft Teams for immediate visibility. For production-critical services, add an incident management channel like PagerDuty or OpsGenie to trigger on-call rotations for Critical-severity incidents.