Skip to content

Quieten noisy alerts

A new tenant can be loud. Work through these steps in order. Each one removes noise at a different level.

  • The admin role for steps 1 to 4, 6 and 7.
  • The member or admin role for step 5.
  • For steps 5 and 6: a workspace with automatic incidents (Super, or the add-on on Pro and Max).

1. Raise the minimum severity on a channel

Section titled “1. Raise the minimum severity on a channel”

If Slack or Teams is too busy, send it less.

  1. Open Alerts under Workspace.
  2. On the channel, raise Minimum severity, for example from WARN to ERROR.
  3. Choose Save changes.

Events still appear in the feed. Only the channel gets quieter.

2. Narrow which tenants a channel receives

Section titled “2. Narrow which tenants a channel receives”

A development tenant rarely needs to page anyone.

  1. On the channel, open Tenant forwarding scope.
  2. Remove the tenants that should not alert this channel.

If one event type floods the feed and nobody acts on it, stop collecting it.

  1. Open Tenants and choose Edit on the tenant.
  2. Remove the event type from the subscribed list.

For Auth0, Select Recommended removes the highest-volume codes in one step. See Change event subscriptions.

If the provider’s severity does not match what the client cares about, override it.

  1. Open Event priorities and create a rule set.
  2. Give the important event types an importance of 4 or 5 and the routine ones 1 or 2.
  3. Apply it to the tenants, or make it the workspace default.
  4. In the feed, switch on Flagged only.

See Prioritise events.

If the same incident keeps opening on one tenant for a known, harmless reason:

  1. Open an incident of that kind. It must involve only one tenant.
  2. Choose Close incident.
  3. Choose the reason False positive. The silence checkbox is offered only for this reason. It is not offered for Benign activity or Resolved.
  4. Tick Silence incidents like this on tenant name.
  5. Choose Close incident.

When it worked: you see the message “Incidents like this will now be silenced on tenant.” with Undo for 15 seconds. Every admin receives an email about the new rule.

What silencing does:

  • Matching incidents at or below this severity still open, but they are listed on the Silenced tab, not on Open.
  • They still collect evidence. If one grows beyond what the rule learned, for example it escalates or shows a new country, it returns to the normal lists on its own.
  • Event alerts to channels are not affected. Use steps 1 to 3 for those.

Without the tick, three False positive closes of the same pattern on one tenant within 30 days arm the same kind of rule. This needs Learn from false-positive closes to be on.

To review the rules, an admin opens Incident settings and reads the Silence rules table on the Learned dismissals card. To bring a pattern back, choose Disarm on the rule’s row, then Disarm rule in the dialog. The rule stays in the table with the state Disarmed. A rule also expires on its own 90 days after it last matched.

Review the Silenced tab regularly. If a silenced incident is a real problem, choose This was real. See Manage incidents.

As a last resort, an admin can switch off a single detector.

  1. Open Incident settings.
  2. On the Automatic incidents card, untick the detector under Workforce detectors or Customer detectors.
  3. Choose Save detectors.

Prefer a silence rule. It applies to one pattern on one tenant and expires when it is no longer needed. A switched-off detector stops for the whole workspace.

To stop the sound without changing anything else, switch on Mute alert sounds under Policies.

What you see Why What to do
The silence checkbox does not appear The reason is not False positive, or the incident involves more than one tenant Choose False positive. An incident across several tenants cannot be silenced.
“Request failed (400)” when you close with the tick The incident is too old to teach a rule Close it without the tick and silence a newer incident of the same kind
The channel still receives alerts after you silenced an incident pattern Silencing applies to incidents only Use steps 1 to 3 for channel alerts
A silenced incident is back on Open It grew beyond what the rule learned. This is a break-out. Treat it as a normal incident
You armed a rule by mistake Undo was not used within 15 seconds An admin disarms the rule in Incident settings
A detector shows Blocked after step 3 You removed an event type it needs Add the event type back. See Manage incidents.
The detector switch did not stay off The change was not saved Choose Save detectors

More messages are listed under Incident settings.