Alert Management workflow nodes
Workflow builder nodes of the Alert Management module.
These nodes appear in the workflow builder when the Alert Management module is available.
This node sends a notification directly to the Frontend, informing the user with the provided notification data. It is essential for delivering real-time updates, alerts, or messages in user-facing applications. The node does not require any additional configuration, making it simple to use for triggering notifications based on dynamic events or system states. The notification data must be structured according to the Notification proto format and is passed into the node for display on the Frontend.
| Name | Description | Type | Required |
|---|
| DataToSent | The notification data to send to the frontend, including message content, type, and additional metadata for display. | group of fields | Yes |
Reads a file path from the payload and attaches the file as evidence to the alert (sent through the dispatch profile). With persist off the file is only sent and then deleted. Attached and Failed carry the incoming payload.
| Name | Description | Type | Required |
|---|
| Value | Payload holding the file path. | group of fields | Yes |
| Name | Description | Type |
|---|
| Attached | Evidence attached. | group of fields (list) |
| Failed | Evidence could not be attached. | group of fields (list) |
| Field | Description | Type | Required | Allowed values | Default |
|---|
| File path path | Payload path holding the file path to attach. | text | Yes | | |
| Kind | Evidence kind. | choice | No | image; audio; file; spectrogram; heatmap | file |
| Use meta alert id | Use the alert ID set in the message meta by RaiseAlert. | yes/no | No | | true |
| Persist | Keep the file as stored evidence of the alert. When disabled the file is only sent through the dispatch profile (same names, order and retry) and the file and its evidence row are deleted once the send succeeded or finally failed. | yes/no | No | | true |
Source node for the evidence flow of a rule alert. alertmanagement starts it once per freshly opened rule alert whose rule carries an evidence_flow label (no run for a repeated firing or an escalation of the same alert). Opened emits a message with observed_at_unix_ms (UTC ms of the trigger), source_module, alert_slug, severity, title and the rule labels as labels; the alert id is set in the message meta, so AttachEvidence (use_meta_alert_id) attaches to the alert. Example: AlertOpened.Opened → AudioClip → AttachEvidence.
| Name | Description | Type |
|---|
| Opened | One message per opened rule alert, the alert id in the meta. | group of fields (list) |
| Field | Description | Type | Required | Allowed values | Default |
|---|
| Alert slug | Emit only for the alert type with this alert_slug (rule alerts carry alert_a-<rule name in kebab case>). Empty = every opened rule alert whose rule carries an evidence_flow label. | text | No | at most 120 characters | |
Looks up the alert by meta alert ID or source reference and routes the payload to Open or Closed. Fail-safe: if the alert is unknown or its status cannot be read, the payload is routed to Open and the reason is noted in the trace, so an escalation is not skipped.
| Name | Description | Type | Required |
|---|
| Value | Payload identifying the alert. | group of fields | Yes |
| Name | Description | Type |
|---|
| Open | Alert is still open, unknown, or its status could not be read. | group of fields (list) |
| Closed | Alert is closed. | group of fields (list) |
| Field | Description | Type | Required | Allowed values | Default |
|---|
| Source ref paths | Payload paths forming the source reference of the alert to look up. | list of text | No | | |
| Use meta alert id | Use the alert ID set in the message meta by RaiseAlert instead of source_ref_paths. | yes/no | No | | |
| Acknowledged counts as closed | Route acknowledged alerts to the Closed output. | yes/no | No | | |
Raises an alert with the configured severity, title and message rendered from the payload. The alert ID is added to the message meta for downstream alert nodes. Raised and Failed carry the incoming payload.
| Name | Description | Type | Required |
|---|
| Value | Payload used for template rendering. | group of fields | Yes |
| Name | Description | Type |
|---|
| Raised | Alert created. | group of fields (list) |
| Failed | Alert could not be created. | group of fields (list) |
| Field | Description | Type | Required | Allowed values | Default |
|---|
| Severity | Severity of the raised alert. | choice | No | ALERT_SEVERITY_INFO (Informational, no action required.); ALERT_SEVERITY_WARN (Warning, worth attention.); ALERT_SEVERITY_ERROR (Error condition, action recommended.); ALERT_SEVERITY_CRITICAL (Critical, immediate action required.) | ALERT_SEVERITY_WARN |
| Title template | Go template for the alert title (receives the payload as '.'). | text | No | at most 200 characters | |
| Message template | Go template for the alert message (receives the payload as '.'). | text | No | at most 5000 characters | |
| Source ref paths | Payload paths forming the source reference that identifies the alert for later resolve/status/evidence nodes. | list of text | No | | |
| Notify owner | Which side dispatches notifications for the raised alert. | choice | No | ALERT_NOTIFY_OWNER_ALERTS (alertmanagement owns the dispatch.); ALERT_NOTIFY_OWNER_SOURCE (The raising module owns the dispatch; alertmanagement stays silent.) | ALERT_NOTIFY_OWNER_SOURCE |
| Alert type | Alert type identifier, e.g. threshold.exceeded. | text | No | at most 100 characters | |
| Dispatch profile | Slug of the AlertDispatchProfile that controls recipients, veto window, evidence and templates. Empty = no profile, existing behaviour. | text | No | at most 120 characters | |
| Pending confirmation | Open the alert as PENDING_CONFIRMATION, so the veto window of the dispatch profile runs before the dispatch fires. The veto only decides whether the dispatch fires, never whether the alert is genuine. | yes/no | No | | false |
| Severity margin | With score_path and threshold_path set, severity is CRITICAL when score >= threshold + margin, else WARN; the fixed severity above is then ignored. | number | No | 0 to 1 | 0.15 |
| Score path | Payload path holding the alert score (0..1). | text | No | at most 200 characters | |
| Threshold path | Payload path holding the threshold in effect at trigger time. | text | No | at most 200 characters | |
| Signals path | Payload path holding the per-source signal list (code and value). | text | No | at most 200 characters | |
| Details path | Payload path holding module-specific details (object). | text | No | at most 200 characters | |
| Triggered at path | Payload path holding the trigger time in UTC ms. | text | No | at most 200 characters | |
| Site slug path | Payload path holding the site slug the alert belongs to. | text | No | at most 200 characters | |
| Veto window s | Veto window in seconds for this alert; overrides the dispatch profile when set. 0 = no window, ACTIVE and dispatched immediately. Unset = use the profile, else 0. | number | No | 0 to 1800 | |
| On finish | Action when the veto window expires unanswered; overrides the dispatch profile when set. Unset = use the profile, else SEND. | choice | No | ALERT_FINISH_ACTION_SEND (The alert becomes ACTIVE and is dispatched.); ALERT_FINISH_ACTION_CLOSE (The alert is closed without dispatch.) | |
Looks up the alert by meta alert ID or source reference and acknowledges or closes it. Resolved and Failed carry the incoming payload.
| Name | Description | Type | Required |
|---|
| Value | Payload identifying the alert. | group of fields | Yes |
| Name | Description | Type |
|---|
| Resolved | Alert acknowledged or closed. | group of fields (list) |
| Failed | Alert not found or could not be updated. | group of fields (list) |
| Field | Description | Type | Required | Allowed values | Default |
|---|
| Action | acknowledge marks the alert as seen; close closes it. | choice | No | acknowledge; close | close |
| Source ref paths | Payload paths forming the source reference of the alert to resolve. | list of text | No | | |
| Use meta alert id | Use the alert ID set in the message meta by RaiseAlert instead of source_ref_paths. | yes/no | No | | true |
This node generates a notification for the Frontend based on a specified trigger. It uses the provided configuration to construct the notification, which is then sent to the Frontend for display. This is useful for creating dynamic notifications that can be triggered by various conditions or events in the system. The configuration must follow the Notification format, which defines the content and structure of the notification.
| Name | Description | Type | Required |
|---|
| Trigger | A boolean trigger that initiates the generation of the notification. When set to true, the node constructs and sends the notification based on the provided configuration. | yes/no | Yes |
| Name | Description | Type |
|---|
| Data | Output for Notification data | group of fields (list) |