stack kb alerting post-alerting-rule-rule-id-alert-alert-id-snooze cli command
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Preview
Preview
Stack
Preview
Preview
elastic stack kb alerting post-alerting-rule-rule-id-alert-alert-id-snooze \
--rule-id <rule-id> \
--alert-id <alert-id> \
[options]
Snooze an alert
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--rule-idstringrequired- The identifier for the rule.
--alert-idstringrequired- The identifier for the alert.
--validate-alerts-existence- Set to
trueto validate that the specified alert exists. If a400error is returned, the specified alert does not exist. Defaults totrue. --condition-operatorenum-
Logical operator applied to the conditions array. "any" expires the snooze when at least one condition is met; "all" requires every condition to be met. When conditions are provided but this field is omitted, defaults to "any".
Values: any, all
--conditionsstring[]-
One or more conditions that, when met, automatically expire the snooze. Supported types:
field_change,severity_change,severity_equals.Repeatable: pass
--conditionsmultiple times to supply more than one value --expires-atstring- The datetime at which the snooze expires, in ISO 8601 format (
YYYY-MM-DDTHH:mm:ss.sssZ). When omitted, the snooze persists indefinitely unless manually removed or a defined condition is met. --input-filestring- path to a JSON file to use as command input
--dry-run- validate all inputs and exit without performing any action (preview changes without applying them)
--no-validate- skip input validation and send the request as-is
--output-fieldsstring- comma-separated list of fields to include in output (dot-notation supported)
--output-templatestring- Mustache-like template for custom text output (e.g. "{{id}}: {{name}}")
--json-
output as JSON