Skip to main content
Version: 1.4 (Current)

Overview

ToBeAlert records a history entry each time an alert changes — status, severity, tags, notes, tool runs, notifications, and more. Use History (Alerts → History) for troubleshooting, accountability, and compliance audits.

StepWhat you doMenu / routeDocumentation
1Browse history records and the hits chartAlerts → History → /historyAlert history tracking · Hits chart and breakdowns
2Narrow with TQL, Current view, time range, or the filters sidebarSame listSearch and TQL · Filters sidebar
3Break down hits by severity, status, resource, and moreHits toolbarBreak down by
4Select rows for details, timeline, export, or deleteSame listBulk actions
5Open a per-alert timelineTimeline (bulk or context menu) → /history/<alertId>Per-alert timeline
6Review the Summary tab or export one alertTimeline viewSummary · Export

History list — hits chart, TQL, filters, and table

Where to find it in the UI​

Entry pointHow
SidebarAlerts → History
From an alertRight-click on the dashboard for history-related actions, or use History in the details drawer
From History listRight-click a row (or use Bulk actions) and choose Timeline
Open timeline vs details

Clicking Alert ID or double-clicking a row opens the point-in-time Details of the alert drawer (state at that history entry). To open the full per-alert timeline, use Timeline from the context menu or bulk actions.

Toolbar highlights on the list:

  • Current view — same views as the dashboard (for example All events)
  • Add filter, TQL search, and time range picker
  • Export filtered view (download icon) and Refresh
  • Hits toolbar: Auto interval / interval presets and Break down by
License

History requires the history feature in your license. If the menu item is disabled, contact your administrator.

What is tracked​

Each history record captures a snapshot of the alert at a point in time, including:

Change type (examples)What you see
NewAlert first received
Status / severity changesPrevious and new values in the timeline
note_added / note_edited / note_deletedNote text. Note edited (note_edited) is recorded only when the note text changes, and the entry shows the new text the same way Note added does. Saving a note without changing the text does not add a row.
Tag, service, attribute updatesAdded, removed, or modified values
Notification sentNotification delivery in the timeline
Tool / plugin executionsReflected as change entries and field updates
Policy execution (cause/effect)A policy marked the alert as an effect: the policy is the actor, the reason names the cause, and the diff shows suppressed and causeId. When a cause is closed, expired, cleared, or deleted, each effect gets a system entry saying it is no longer suppressed — see Cause and effect alerts

History records include the user (or system / plugin / scheduled task) who performed an action when applicable — see Users and permissions.

ModuleRelationship
Hits chart and breakdownsVolume over time and stacked breakdowns
Per-alert timelineChanges + Summary for one alert
TQL search and filtersShared TQL syntax; History list is TQL-only
List tables and bulk actionsShared table chrome
Alerts dashboardContext menu and drawer history
Running tools on alertsTool runs appear in alert history
Notification rulesNotification sent entries in the timeline; rule-run history is under Notifications → Rules → All executions
PoliciesCross-check when alert fields change unexpectedly
Not the same as Tools / Policies / Notification rules history

Tools → All executions (/tools/history), Policies → All executions (/policies/history), and Notifications → Rules → All executions (/notifications/rules/history) are entity run histories, not alert change audit. Metrics History on /metrics is aggregated metrics history — also separate from Alerts → History.

Best practices​

See Alert history tracking — Best practices and Hits chart tips.