Skip to main content

Monitors and alerts

Open Monitors for personal real-time monitors. In an organization, open Monitoring from the selected client space or asset scope; it has a separate review inbox, collection schedules and budget. See Organization monitoring.

Create or edit a personal monitor​

  1. Choose Create monitor and a dataset available to your account.
  2. Enter the query and use the editor's validation/preview. Review the resulting scope before saving.
  3. Select delivery: Daily digest, Immediate email or Real-time, according to the available options.
  4. Name and save the monitor, then check its validation and activation state in the list. Editing and duplication use the same editor.

Existing advanced regular-expression rules remain editable. A search query is not itself a regex: use the editor's conversion and validation. If a rule cannot be converted safely, keep or edit its advanced definition rather than discarding it.

The dataset choices and active-monitor/hourly limits come from your account. Free accounts cannot enable paid alerting. A saved but paused monitor is different from an active one.

What triggers an alert?​

Personal monitors match newly ingested observations through the alerting engine. They do not replay an entire historical search or poll a site's uptime. Existing indexed records can be found with Search; an absence of alerts is not proof that nothing changed on the target.

Daily digest groups eligible events into a scheduled email; it does not send a message merely because the monitor exists. Immediate email and Real-time use their selected delivery paths. An enabled monitor and a working integration are separate requirements.

Check delivery​

Use Delivery to configure the notification integration and inspect its status. Use Test lab to test matching against a sample record; only explicit send/test-delivery actions send a notification. See Hosted delivery.

If an integration reports an error, check its current destination/credentials and test it after saving. A successful matching test alone does not prove that the external provider accepted a delivery.

Troubleshoot​

SymptomAction
Pending or invalid ruleInspect the validation message and narrow the query
Paused monitorCheck activation, plan capacity and credits before re-enabling
Too many matchesNarrow the rule and review the hourly limit
No digest yetConfirm digest delivery is enabled and that eligible new events exist
Matching succeeds but delivery failsInspect Delivery and verify the configured destination
Session expiredSign in again; do not repeatedly recreate the integration

The page's monthly credit figure is an estimate from recent rates, not a guaranteed bill. Check Credits for base rates. Changing notification settings does not collect historical data.