AlertRuleDto
Full presentation model for an Alert Rule
{
"id": "string",
"alertRuleId": 0,
"name": "string",
"trigger": "string",
"triggerType": "string",
"triggerValue": "string",
"scope": "string",
"groupScopeId": 0,
"threshold": "string",
"thresholdCount": 0,
"thresholdWindow": "string",
"delivery": "string",
"deliveryType": "string",
"recipient": "string",
"enabled": false,
"revision": 0,
"ruleSource": "string",
"systemKey": "string",
"createdAt": "string",
"updatedAt": "string"
}
String identifier matching frontend requirements
Unique canonical Alert Rule identifier
Human-readable rule name
Display-friendly trigger label (e.g. Outcome = Enforced (blocked))
Supported architectural trigger classification for Alert Rules
OUTCOME: The rule fires on events with a given outcome (ALLOWED, DETECTED_OBSERVE, PREVENTED, TERMINATED or ERROR)EVENT_CLASS: The rule fires on events of a given class (EXEC, FILE, NET, CONFIG, BEHAVIORAL or TAMPER)EVENT_CATEGORY: The rule fires on events of a given category (PROCESS_EXECUTION, FILE, NETWORK or SYSTEM_CALL)LICENSE_EXPIRY: The built-in license expiration rule. It is not event-driven: its alerts are created by the licensing scheduler, the event engine never evaluates it, and a rule cannot be created or retargeted to this type
Canonical trigger value matching schema enums
Display scope label (e.g. All Hypervisors or group name)
Target Security Group identifier (null for fleet-wide)
Display-friendly threshold expression
Number of events required to breach threshold
Evaluation lookback window for threshold breach detection
ANY_OCCURRENCE: No fixed period: a single matching event qualifies. The default of a rule; the engine looks back only a short period derived from its sweep interval, at least 10 secondsONE_MINUTE: Matching events are counted over a 60-second lookback; a threshold text such as 5 in 1 minute selects it when the stated minutes are below 5FIVE_MINUTES: Matching events are counted over a 300-second lookback; a threshold text selects it when the stated minutes are 5 or more
Formatted delivery description. A webhook destination in it is masked for the AUDITOR role, see recipient.
Outbound delivery channel type
Delivery destination (email address or webhook URL). The AUDITOR role receives a webhook destination masked to scheme and host (e.g. https://hooks.example.com/…); ADMIN and SECURITY_OPERATOR receive it in full.
Whether the rule is actively evaluated
Monotonically increasing semantic revision number
Rule provenance origin
SYSTEM: Built-in rule. It cannot be deleted or renamed and its trigger, threshold and scope cannot change; only the enabled flag and the delivery settings canCUSTOM: Rule created through the API by a user
Stable system identifier for built-in rules (null for custom rules)
Creation timestamp
Last update timestamp