Alerts and rules

Use Runtime → Alerts to watch recorded terminal activity for the selected workspace. Each alert rule runs on a schedule, applies the same style of filters as reports, and stores a match. Matching runs can email a recipient list.

The Alerts tab is available when the alert engine is enabled for the tenant.

Before you start

1. Open Account → Settings.
2. Under Email, set the SMTP host, port, security, and from address. Add credentials if the server requires them, then test the connection.
3. Under Alert engine, turn on Enable alert rules.
4. Select a workspace in the top bar.

Create a rule

1. Open Runtime → Alerts and choose Add rule.
2. Set the name, description, schedule, and optional cooldown.
3. Build filters with Filter by and nested AND, OR, and NOT groups. Conditions cover screen, action, user, field comparisons, steps, and duration.
4. Choose a recipient list, or create one under Recipient lists.
5. Edit the email subject and body, or choose Generate message to draft them from the conditions. Tokens include ${rule}, ${user}, ${session}, ${screen}, ${time}, ${count}, and ${link}.
6. Save the rule and leave it on.

Run now and history

Run now evaluates the rule immediately. The page reports new alerts, matches that were already alerted, no new matches, or an error.

Alert history lists raised alerts. When the deployment has an application URL, each email can link back to the matching session and event.

Notes

• A new rule starts from current traffic. It does not alert on older events.
• Password-style fields are not offered as message tokens.