Change global alert rules
Partial: only the listed rules and the fields present change. Null resets a severity or a threshold to its default. The values that result for each service must be valid, else 400 names the service. Regenerates and reloads the rule file, so a change takes effect immediately.
/api/v1/alert-rulestse_sessionAPI key · cookierequiredapplication/jsonrulesAlertRuleUpdate[]requiredShow propertiesHide properties
AlertRuleUpdateenabledboolean | nullOmit to keep; null resets to the default (on)
namestringrequiredseveritystring | nullOmit to keep; null resets to the rule default
warningcriticalthresholdinteger<int64> | nullOmit to keep; null resets to the default
OK
rulesAlertRuleSetting[]requiredShow propertiesHide properties
AlertRuleSettingconfigurablebooleanrequiredFalse for the heartbeat
defaultSeveritystringrequiredwarning or critical; empty for the heartbeat
enabledbooleanrequiredgroupstringrequiredinfrastructuredatabaseconsolenamestringrequiredscopestringrequiredservice rules can be overridden per database service
serviceconsoleseveritystringrequiredThe global severity; empty for the heartbeat
summarystringrequiredthresholdAlertRuleThreshold | nullrequirednull when the rule has no threshold
Show propertiesHide properties
defaultinteger<int64>requiredThe shipped default
labelstringrequiredWhat the number means
maxinteger<int64>requiredmininteger<int64>requiredunitstringrequiredpercenthourssecondsdaysvalueinteger<int64>requiredThe global value
nullError
codestringStable code of the refusal, when the route has codes
detailsstring[]Additional detail, e.g. per-field validation failures
errorstringrequiredHuman-readable error message