View execution history
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. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability We plan to add this functionality in a future Elastic Stack update. Subject to changes. 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 Security
Preview
Preview
Stack
Planned
Planned
Each time a Worker runs, Kibana records the run. Use the execution history to check that a Worker is running on schedule, to see what a run did, and to find out why a run failed. The history includes scheduled runs and runs that you start yourself.
- Turn on the Show managed workflows advanced setting. Because each Worker is a managed workflow, you can't see its runs while managed workflows are hidden. Refer to Set up Workflows > Show managed workflows.
- Make sure your role includes the privilege to read the executions of managed workflows. Refer to Grant access to AlertZero > Let administrators set up and manage Workers.
- Find Watches in the navigation menu or use the global search field.
- Open the Watch that contains the Worker.
- In the Worker's settings, select View executions. The Worker's execution history opens in the workflow editor.
- Select a run to see its logs, including what each step did.
If a run fails, open it and find the step with the error indicator to see what went wrong. For troubleshooting steps, refer to Monitor workflow execution.
To see what a run produced, such as proposed actions, refer to Work in AlertZero.
Runs that you start from the workflow editor are test runs. They're saved with a flask badge, so you can tell them apart from scheduled runs and from runs that you start from the workflow list. Refer to Use the YAML editor > Test runs and production runs.