Disable or Delete a Notification Channel

Sometimes, a notification channel has outlived its use, or must be temporarily disabled due to noise while an underlying issue is investigated. Follow this page to disable and mute notification channels.

Temporarily Disable a Notification Channel

To temporarily disable a notification channel:

  1. Log in to Sysdig Monitor or Sysdig Secure as administrator.

  2. Select Settings > Notification Channels.

  3. Identify a channel, and toggle the Enabled slider off.

To re-enable the channel, toggle the slider on.

Mute Notifications During Downtime

Admin users can prevent all notifications for all Sysdig teams from being forwarded to every notification channel.

To achieve this:

  1. Log in to Sysdig Monitor as an Admin.

  2. Select Settings > Notification Channels.

  3. Toggle Downtime on to temporarily disable alert events and mute all notifications.

A confirmation window appears.

  1. Optional: To notify channels that notifications are temporarily disabled, tick the box Notify via e-mail or Slack. Select channels you wish to notify from the drop-down.

The Downtime toggle lets you silence all notification channels during, for example, a scheduled system downtime.

Delete a Notification Channel

  1. Log in to Sysdig Monitor or Sysdig Secure as administrator.

  2. Select Settings > Notification Channels.

  3. Select the three-dot menu icon on the right side of a channel listing.

  4. Select Delete Channel.

Configure an Alert Start-Up Delay (On-Premises Only)

Sysdig alert jobs begin immediately at start-up. However, in instances where Sysdig goes down unexpectedly, or without proper shutdown/startup procedures implemented, data can be missing, triggering alert notifications.

A start-up delay in alert jobs can be configured in on-premises environments, by setting the draios.alerts.startupDelay parameter. The parameter requires a duration value; the example below shows a duration of 10 minutes:

draios.alerts.startupDelay=10m

This parameter can be configured for Kubernetes environments:

  • For Kubernetes environments, add the parameter to the sysdigcloud.jvm.worker.options parameter in the configmap.

For more information on editing the configmap refer to the On-Premises Installation documentation.