stack kb security-osquery-api osquery-get-unified-history 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 security-osquery-api osquery-get-unified-history [options]
Get unified query history
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--page-sizenumber- The number of results to return per page.
--next-pagestring- A base64-encoded cursor for pagination. Use the value from the previous response to fetch the next page.
--kuerystring- A search string to filter history entries by pack name, query text, or query ID.
--user-idsstring- Comma-separated list of user IDs to filter live query history.
--source-filtersstring- Comma-separated list of source types to include. Valid values are
live,rule, andscheduled. --start-datestring- The start of the time range filter (ISO 8601).
--end-datestring- The end of the time range filter (ISO 8601).
--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