How can we help?

Understanding Alert Notification Channel Inheritance

Follow

Overview

In Auvik, alert notification channels (such as email, webhook, or integrations) can be configured at multiple levels, including the root site, child sites, and individual alert rules.

By default, alert configurations follow the notification channels defined at the root site. This allows centralized control over alert recipients, but it can also lead to unexpected behavior if the inheritance model is not clearly understood.

This article explains how notification channel inheritance works and how to review and adjust alert recipients.


How Notification Channel Inheritance Works

Root Site Configuration

The root site acts as the primary source of notification channels.

  • When you add a notification channel at the root site, it is applied to:
    • Child sites
    • Alert rules
      that have not been customized
  • If the root site previously had no channels configured, adding one will immediately cause alerts that follow the root configuration to begin sending notifications.

Inheritance Is the Default State

Alert rules and child sites will continue using the root site’s notification channels as long as their configuration has not been modified.

There is no separate control to enable or disable inheritance—this behavior is automatic.


Customization Stops Inheritance

Inheritance is implicitly overridden when notification channels are modified at the site or alert rule level.

Examples of modifications include:

  • Adding a new notification channel
  • Removing an existing channel
  • Replacing the channel list

Once changes are made:

  • The alert rule or site uses its own defined channels
  • It will no longer follow updates from the root site

Changes Apply Immediately

Updates to notification channels take effect right away:

  • Adding a channel at the root → alerts begin sending to it immediately (if still following root)
  • Removing a channel at the root → alerts stop sending to it immediately

No Automatic Reversion

Removing a notification channel does not restore any previous configuration.

  • Channels must be manually re-added if needed
  • There is no rollback to prior settings

How to Check Where Alerts Are Sent

To confirm who receives alerts:

  1. Open the relevant:
    • Alert rule, or
    • Site-level alert settings
  2. Locate the Notification Channels section
  3. Review the list of channels displayed

The channels shown represent the actual destinations that will receive alerts.


How to Adjust Alert Recipients

Define Custom Notification Channels

To use different recipients than those defined at the root:

  1. Open the alert rule or site settings
  2. Locate the Notification Channels section
  3. Modify the list of channels (add, remove, or replace)

Once changes are made, the configuration becomes independent of the root site.


Limit Alerts to Specific Recipients

If alerts are being sent to too many recipients:

  • Update the notification channels at the:
    • Child site level, or
    • Individual alert rule level

This ensures only the intended recipients receive alerts.


Verifying Configuration

After making changes:

  • Trigger a test alert, or
  • Review the alert configuration preview (if available)

Confirm that the expected notification channels are listed and receiving alerts.


Key Points

  • Notification channels at the root site apply by default
  • Inheritance continues until the configuration is modified
  • There is no explicit “disable inheritance” control
  • Modifying channels creates an independent configuration
  • Changes take effect immediately
  • Always verify the Notification Channels list to confirm recipients
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request