Skip to main content

Documentation Index

Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

Notifications help you turn monitored events into timely human action. A notification group defines who should receive alerts, which channels are used, what topics matter, and when alerts should be muted.

​
Prerequisites

  • You know which team should respond to each event class.
  • The intended recipients exist as users or notification-only users.
  • Any external channel integration you want to use has been configured.

​
Notification Groups

A notification group can define:
  • Recipients
  • Channels
  • Topics
  • Site scope
  • Schedules
  • Muting behavior
Use groups to keep alert routing readable. For example, a network operations group might receive site offline and WAN degradation alerts, while a customer success group receives only scheduled SLA reports.

​
Create a Group

  1. Open Notifications and select Groups.
  2. Create a group with a purpose-driven name.
  3. Add users or notification-only recipients.
  4. Select the channels the group should use.
  5. Select topics and site scope.
  6. Configure schedule or muting behavior if the group should not receive alerts at all times.
  7. Save the group.

​
Where Groups Are Used

Notification groups can be selected by monitoring and reporting features, including fault alerting and SLA report schedules. Workflows can also send notifications as part of an automated response.

​
Advanced Use Cases

Use separate groups for severity and audience. Critical site outages may go to on-call engineers, while weekly reports go to managers or customers. Use muting during planned maintenance windows so expected events do not create unnecessary noise. After maintenance, remove or expire the mute so real incidents are routed again.
Notification-only users are useful when someone needs alerts or reports but should not sign in to the portal. See User and Team Management.