ConHiveConHive Docs
ModulesAlert Management

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.

Notification Frontend

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.

Inputs

NameDescriptionTypeRequired
DataToSentThe notification data to send to the frontend, including message content, type, and additional metadata for display.group of fieldsYes

Attach Evidence

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.

Inputs

NameDescriptionTypeRequired
ValuePayload holding the file path.group of fieldsYes

Outputs

NameDescriptionType
AttachedEvidence attached.group of fields (list)
FailedEvidence could not be attached.group of fields (list)

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
File path pathPayload path holding the file path to attach.textYes
KindEvidence kind.choiceNoimage; audio; file; spectrogram; heatmapfile
Use meta alert idUse the alert ID set in the message meta by RaiseAlert.yes/noNotrue
PersistKeep 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/noNotrue

Alert Opened

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.

Outputs

NameDescriptionType
OpenedOne message per opened rule alert, the alert id in the meta.group of fields (list)

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
Alert slugEmit 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.textNoat most 120 characters

Alert Status

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.

Inputs

NameDescriptionTypeRequired
ValuePayload identifying the alert.group of fieldsYes

Outputs

NameDescriptionType
OpenAlert is still open, unknown, or its status could not be read.group of fields (list)
ClosedAlert is closed.group of fields (list)

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
Source ref pathsPayload paths forming the source reference of the alert to look up.list of textNo
Use meta alert idUse the alert ID set in the message meta by RaiseAlert instead of source_ref_paths.yes/noNo
Acknowledged counts as closedRoute acknowledged alerts to the Closed output.yes/noNo

Raise Alert

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.

Inputs

NameDescriptionTypeRequired
ValuePayload used for template rendering.group of fieldsYes

Outputs

NameDescriptionType
RaisedAlert created.group of fields (list)
FailedAlert could not be created.group of fields (list)

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
SeveritySeverity of the raised alert.choiceNoALERT_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 templateGo template for the alert title (receives the payload as '.').textNoat most 200 characters
Message templateGo template for the alert message (receives the payload as '.').textNoat most 5000 characters
Source ref pathsPayload paths forming the source reference that identifies the alert for later resolve/status/evidence nodes.list of textNo
Notify ownerWhich side dispatches notifications for the raised alert.choiceNoALERT_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 typeAlert type identifier, e.g. threshold.exceeded.textNoat most 100 characters
Dispatch profileSlug of the AlertDispatchProfile that controls recipients, veto window, evidence and templates. Empty = no profile, existing behaviour.textNoat most 120 characters
Pending confirmationOpen 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/noNofalse
Severity marginWith score_path and threshold_path set, severity is CRITICAL when score >= threshold + margin, else WARN; the fixed severity above is then ignored.numberNo0 to 10.15
Score pathPayload path holding the alert score (0..1).textNoat most 200 characters
Threshold pathPayload path holding the threshold in effect at trigger time.textNoat most 200 characters
Signals pathPayload path holding the per-source signal list (code and value).textNoat most 200 characters
Details pathPayload path holding module-specific details (object).textNoat most 200 characters
Triggered at pathPayload path holding the trigger time in UTC ms.textNoat most 200 characters
Site slug pathPayload path holding the site slug the alert belongs to.textNoat most 200 characters
Veto window sVeto 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.numberNo0 to 1800
On finishAction when the veto window expires unanswered; overrides the dispatch profile when set. Unset = use the profile, else SEND.choiceNoALERT_FINISH_ACTION_SEND (The alert becomes ACTIVE and is dispatched.); ALERT_FINISH_ACTION_CLOSE (The alert is closed without dispatch.)

Resolve Alert

Looks up the alert by meta alert ID or source reference and acknowledges or closes it. Resolved and Failed carry the incoming payload.

Inputs

NameDescriptionTypeRequired
ValuePayload identifying the alert.group of fieldsYes

Outputs

NameDescriptionType
ResolvedAlert acknowledged or closed.group of fields (list)
FailedAlert not found or could not be updated.group of fields (list)

Settings

FieldDescriptionTypeRequiredAllowed valuesDefault
Actionacknowledge marks the alert as seen; close closes it.choiceNoacknowledge; closeclose
Source ref pathsPayload paths forming the source reference of the alert to resolve.list of textNo
Use meta alert idUse the alert ID set in the message meta by RaiseAlert instead of source_ref_paths.yes/noNotrue

Generate Notification

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.

Inputs

NameDescriptionTypeRequired
TriggerA 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/noYes

Outputs

NameDescriptionType
DataOutput for Notification datagroup of fields (list)