Skip to main content
Altostrat Notifications transform your monitoring from reactive to proactive. Instead of constantly watching dashboards, you can configure the platform to automatically alert the right people, through the right channels, the moment a critical event occurs. The entire notification system is built around Notification Groups. A Notification Group is a powerful routing rule that defines who gets notified about what, for which sites, and when.

​
How Notification Groups Work

Each Notification Group is a collection of four key components that work together to deliver targeted alerts.

​
Creating a Notification Group

1

1. Navigate to Notification Groups

In the SDX dashboard, go to Notifications → Notification Groups. Click + Add to create a new group.
2

2. Define the Group and Recipients (WHO)

  1. Give the group a descriptive Name (e.g., “Critical Site Outage Alerts”).
  2. In the Recipients section, add the users who should receive these alerts and select their preferred Channel (e.g., Email, WhatsApp).
3

3. Select Topics (WHAT)

Choose the event categories (Topics) that this group should be notified about. Common critical topics include:
  • Heartbeat Failures: A device has gone offline.
  • WAN Failover Events: A primary internet link has failed.
  • Security Alerts: A threat has been detected and blocked.
4

4. Assign Sites (WHICH)

Specify which sites this notification rule applies to. You can select all sites or choose specific ones. For example, you might create a group that only sends alerts for your high-priority data center sites.
5

5. Configure Schedule and Muting (WHEN)

Link a schedule to the group to define its active hours. Combined with the Mute setting, you can create sophisticated on-call logic, such as only sending alerts to a specific team during their business hours.
6

6. Save the Group

Click Save. Your new notification rule is now active. When an event occurs that matches all the criteria you’ve defined, an alert will be sent.

​
Best Practices

Be Specific

Create multiple, specific groups instead of one large, noisy one. For example, a “Security Team” group for security alerts and a “NOC Team” group for outage alerts.

Respect On-Call Hours

Use schedules and muting rules to avoid alert fatigue. Send non-critical alerts only during business hours, and reserve after-hours notifications for genuine emergencies.

Integrate with Your Workflow

Connect your notifications to external tools like Slack or Microsoft Teams. This allows your team to receive and discuss alerts within the collaboration tools they already use.