Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Lakewatch is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage workspace-level previews.
An alert groups signals so you can investigate related activity together.
Tip
You can triage an alert with Genie Code from its detail page. See Triage alerts with Genie.
How are alerts created?
Lakewatch creates alerts automatically, and you can't create an alert manually. When a detection rule fires, Lakewatch groups related signals into a single alert through signal grouping rather than opening a new alert for every signal. A new signal attaches to an existing alert when all of the following conditions are met:
- The signal shares the same rule ID, rule version, and summary as the signal that opened the existing alert.
- The existing alert was opened within the collation window, which determines how long an alert stays open to collect matching signals. The collation window defaults to 1 hour and is configurable per catalog in Settings.
- The existing alert is still in the Open or In progress state.
Lakewatch creates a new alert when no matching alert exists, the most recent matching alert was opened before the collation window, or the matching alert is resolved or marked as a duplicate.
The grouping criteria (rule ID, rule version, and summary) can't be customized, but you can change the collation window per catalog. Signal grouping is separate from signal deduplication, which runs earlier: deduplication drops identical signals as they're created, and grouping then organizes the surviving signals into alerts.
Note
An alert is grouped on the summary of the signal that opened it. When a rule fires, Lakewatch matches each new signal against the opening signal's summary, so the two summaries must be identical for the signals to land in the same alert.
A rule's summary is a template that can interpolate event data with {sql-expression} placeholders, and grouping compares the rendered text. If the summary includes a value that differs on every match, such as a timestamp or event ID, each signal renders a unique summary and opens its own alert instead of grouping. If a rule opens far more alerts than expected, check whether its summary can be generalized.
# Too specific: {time} differs on every event, so every failed login opens its own alert
summary: "Failed login by {actor.user.name} at {time}"
# Better: all of a user's failed logins render the same summary and group into one alert
summary: "Failed login by {actor.user.name}"
Alert limit for noisy rules
Each version of a detection rule can open at most 1,000 new alerts within a rolling 24-hour window. There is no limit on the number of signals a rule can produce.
When a rule version reaches the limit, Lakewatch stops opening new alerts for it and instead groups all further signals from that rule version into a single overflow alert with the summary "Too many events detected for rule [rule ID]", so a noisy rule can't flood the alert list. The overflow alert is a regular alert: it appears in the alert list with severity inherited from the rule, and you can assign, comment on, and resolve it like any other alert. An overflow alert has a fixed collation window of 24 hours: while a rule version is over its limit, new signals attach to an existing open overflow alert from the past 24 hours if one exists, and otherwise open a new overflow alert.
Normal alert creation resumes automatically when the rule version's 24-hour alert count drops back below the limit. Because the limit is tracked per rule version, updating the rule (for example, tuning its query so it produces fewer distinct signals) also starts a fresh count.
Working with alerts
To manage alerts, navigate to Alerts. On the alerts list, you can:
- Search and filter: Search alert titles, descriptions, and comments. Filter by state, severity, assignee, detection rule, and creation date. You can select more than one state or severity. Search and filter selections persist across navigation within Lakewatch, and the active filter state is reflected in the URL. Copy the URL to share or bookmark a filtered view.
- By default, the list shows Active alerts (Open, In progress, and Mitigated) with Critical, High, Medium, or Low severity. Informational alerts and Resolved or Duplicate alerts are hidden until you change the State or Severity filter. Removing a filter restores these defaults.
- Assignee filters to Anyone, Unassigned, Assigned to me, or a specific user.
- Created offers presets from Last hour to Last 6 months, or a custom start and end date and time in a time zone you choose.
- View the list: See all alerts in the current environment that you can access, 50 per page. The list displays columns for the alert title, severity, state, Exported to, signal count, assignee, and created and updated timestamps. The alert ID and detection rule name appear under each alert title. Columns are sortable and resizable.
- Edit from the list: Click an alert's severity, state, or assignee in its row to change it without opening the alert.
- Bulk actions: Select alerts on the current page, or select the whole page, then click Assign selected or Set state to update them all at once. Changing a filter, the sort order, or the page clears your selection.
- Open details: Click an alert title to open the alert details page, where you can view signals and edit attributes.
Alert details
Click an alert title to open the alert details page. The header shows the alert title, the alert ID, the state, and the severity. You can change the state from the header. The details panel lists the alert attributes, where you change the assignee, severity, and classification.
The page is organized into two tabs:
- Overview: Displays the description and comments.
- Format comments with the editor toolbar, which supports bold, italic, headings, links, lists, task lists, quotes, and code.
- Click Reply to reply to a comment. Replies appear under the original comment.
- You can edit or delete your own comments and replies, but not other users' comments.
- Use the sort menu to show Newest first or Oldest first.
- Signals: Lists the signals that are grouped into this alert, with the signal count on the tab. Search the loaded signals, or click a signal to open its details in a side panel, including its actors and resources, signal ID, event and detected times, the rule that generated it, and the full signal record.
To investigate the alert with Genie, click Triage with Genie at the top of the details panel. If you've triaged the alert before, the button reads Resume triage. See Triage alerts with Genie.
Alert attributes
Each alert has the following editable attributes:
- Assignee: The user responsible for the investigation. Defaults to "Unassigned".
- State: One of Open, In progress, Mitigated, Resolved, or Duplicate.
- Severity: Inherited from the detection rule associated with the first signal connected to the alert. You can manually override severity at any time.
- Classification: Indicates whether the activity captured in the alert is a real threat. Choose False positive, Benign positive, or True positive (or Unspecified if not yet triaged).
Each alert also has the following read-only attributes:
- Alert ID (seq_id): A system-generated display ID, such as
SEC-42, shown under the alert title. Click Copy ID to copy it. The ID is unique within a workspace, not across workspaces. - Alert title: System-generated summary of the alert. Immutable; cannot be edited. Based on the detection rule's summary template.
- Description: The detection rule's description, shown on the Overview tab.
- Permalink: A stable link to the alert (the seq_id). Copy it with the Copy permalink button.
- Rule: The detection rule that produced the alert's signals.
- Run as: The identity that created the alert, which is the user or service principal the detection rule runs as.
- First/Last event: The times of the first and most recent events associated with the alert.
- Signal count: The number of signals attached to the alert, shown on the Signals tab and in the alert list. This count is approximate and can lag, especially under high signal load.
- Created at: Timestamp of when the alert was created.
- Updated at: Timestamp of when the alert was last modified.
Exporting alerts
Export alerts to an external system, such as ServiceNow, Tines, a webhook, or Jira, so your team can track and act on them in the tools it already uses. For destinations and setup, see Alert destinations.
To check an alert's export status:
- In the alert list, the Exported to column shows a logo for each destination the alert was exported to, marked when the export failed, is in progress, or wasn't confirmed. Hover over a logo to see what happened. A dash means the alert has no recorded export.
- On the alert details page, the Export attribute lists each destination with the export status, the reason for any failure, and a link to the record the export created.