BatchUpdateRules
Updates existing rules or creates rules that do not exist.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
If validate_only is true, the request will only validate the request and not save the rules.
Discouraged escape hatch for saving rules whose expression cannot be fully validated
server-side. When true:
- Per-asset expression validation errors (e.g. channel not present on the in-scope asset)
are returned in
validation_resultsfor visibility but do not block the save. - If the rule's UDF/calculated-channel inlining cannot resolve types (typically because
the referenced channels haven't been ingested yet, or there are too many distinct
identifiers for the type-inference budget) the rule is still persisted, but its
is_live_evaluation_enabledis forced tofalse. Live alerts will skip it; report generation and on-demandEvaluateRulescalls still work because they re-resolve types at run time. To bring such a rule back online, fix the underlying problem (ingest the channels, simplify the expression, etc.) and reissue an update withis_live_evaluation_enabled = true.
Marked deprecated = true because new integrations should validate input before
submitting; existing SDK call sites that rely on this flag continue to work.
Response
A successful response.
The total number of rules created in the request. If validate_only is true, this will indicate how many rules would have been created.
The total number of rules updated in the request. If validate_only is true, this will indicate how many rules would have been updated.
This will be true if the request only validated the request and did not save the rules.
The created rule id, name, version, and client key.