stack kb alerting-v2 get-alerting-v2-execution-history-action-policies 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-v2 get-alerting-v2-execution-history-action-policies \
--page <page> \
--per-page <per-page> \
--sort-field <sort-field> \
--sort-order <sort-order> \
[options]
List action policy executions
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--pagenumberrequired- Page number (1-indexed). Defaults to 1.
--per-pagenumberrequired- Number of events per page. Defaults to 20.
--sort-fieldenumrequired-
Sort field. Defaults to "dispatched_at".
Values: dispatched_at
--sort-orderenumrequired-
Sort direction. Defaults to "desc".
Values: asc, desc
--fromstring- Inclusive ISO datetime lower bound on the event timestamp; overrides the default 24-hour window. Independent of alert_ids — e.g. set it to an alert’s start time to scope results to that alert’s lifetime.
--tostring- Inclusive ISO datetime upper bound on the event timestamp.
--alert-idsstring[]-
Alert filter. Narrows events to those referencing at least one of the provided alert IDs.
Repeatable: pass
--alert-idsmultiple times to supply more than one value --searchstring- Free-text search. Matches policy name, rule name, policy/rule ID (case-insensitive).
--rule-idsstring[]-
Explicit rule filter. Narrows events to those referencing at least one of the provided rule IDs. Also unions with the search filter if both are provided.
Repeatable: pass
--rule-idsmultiple times to supply more than one value --outcomesstring[]-
Outcome filter. When omitted matches all outcomes. Pass one or more of "success", "throttled", "failure" to narrow.
Repeatable: pass
--outcomesmultiple times to supply more than one value --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