Skip to Content

Alarms

Define alert rules over the audit log and get notified by email when important events happen.

RequiresAdvanced+

Plan required: Alarms are available on the Advanced and Pro plans (and during the trial).

Alarms watch the audit log and notify you by email when events match a rule you define. Use them to stay on top of security-relevant activity, such as a burst of failed logins, an admin role being granted, or a connector going offline, without having to watch the log yourself.

You find alarms under Audit Trail → Alarms in the Admin Console.

Create an alarm

  1. Go to Audit Trail → Alarms and select Create alarm.
  2. Pick a ready-made template (for example Brute force detected or Admin role changed) or choose Start from scratch.
  3. Give the alarm a name and a severity (Info, Warning, or Critical). The severity is your own label; it appears in the list and in the email subject.
  4. Under Condition, select the event types the alarm reacts to. Optionally restrict it to specific users, applications, directories, workspaces, or network zones. A workspace scope matches events attributed to the workspace as well as events of its current applications and APIs. Applications selected together with a workspace widen the scope instead of narrowing it: the alarm then reacts to events of the workspace and of those applications. The other restrictions (users, directories, network zones) still narrow it.
  5. Choose how the alarm fires (see Firing modes).
  6. Under Recipients, add the admins and any extra email addresses that should be notified. With a workspace scope you can additionally enable Notify workspace responsibles; the responsibles of the selected workspaces are resolved each time the alarm fires.
  7. Optionally use Test alarm to see how many matching events occurred recently, then save.

New alarms only evaluate events that happen after they are created; existing history never triggers a notification.

Firing modes

An alarm fires in one of two ways:

  • On every matching event: a notification is sent as soon as a matching event appears. A cooldown then keeps the alarm quiet for a chosen period, so a stream of the same event does not flood your inbox.
  • When a threshold is reached: a notification is sent when at least N matching events occur within a time window (for example, at least 10 failed logins within 5 minutes). Events can be counted overall, per user, or per IP address. When counted per user or per IP, each user or address is tracked separately.

Example (brute force): select the failed-login event types, choose When a threshold is reached, set at least 10 events within 5 minutes, and count per IP address. Each attacking address that crosses the threshold produces its own notification.

Test an alarm

The Test alarm button runs the current rule against recent history and shows how many events it matches, with a sample. It is a dry run: no notifications are sent. Use it to tune a rule before saving so it is neither too noisy nor too quiet.

Trigger history

Every time an alarm fires it is recorded on the Triggered tab (and on each alarm's own History tab): when it fired, how many events matched, and whether each recipient's email was sent or failed. From an entry you can jump straight to the matching events in the audit log. New entries are highlighted until you open the Triggered tab.

Rate limiting

To prevent notification storms, alarm email is capped in two ways:

  • Each alarm can send a limited number of notifications per hour.
  • Each tenant has an overall hourly limit on alarm emails. The trial plan has tighter limits.

When a limit is reached, the alarm still records that it fired, but the email is withheld and the entry is marked Rate-limited. If you see this, raise the cooldown, narrow the rule, or switch to threshold mode.

Reference

FieldNotes
SeverityInfo, Warning, or Critical. Your own label; shown in the list and email subject.
Event typesOne or more audit event types the alarm reacts to. See Audit event types.
ScopeOptional restriction to specific users, applications, directories, workspaces, or network zones (zones defined by IP ranges).
ModeOn every matching event or When a threshold is reached.
ThresholdCount, time window, and how to count (overall, per user, per IP).
CooldownHow long the alarm stays quiet after firing (applied per group when counting per user or IP).
RecipientsAdmins, additional email addresses, and optionally the responsibles of the scoped workspaces. At least one is required.
RetentionTrigger history is kept for 90 days.

Troubleshooting

  • No email received. Open the triggered entry and check the delivery status. A Failed status shows the mail error; confirm your email provider is configured under Branding → Mail. Also check whether the alarm was within its cooldown or marked Rate-limited.
  • The alarm never fires. Alarms only evaluate events that occur after the rule is created or last edited. Confirm the selected event types actually occur, and use Test alarm to check the filter.
  • Too many emails. Raise the cooldown, narrow the event types or scope, or switch to threshold mode so only a burst triggers a notification.

See also

On this page