Conditions
The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. 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.
Stack
Generally available
When a watch is triggered, its condition determines whether or not to execute the watch actions. Watcher supports the following condition types:
always: The condition always evaluates totrue, so the watch actions are always performed.never: The condition always evaluates tofalse, so the watch actions are never executed.compare: perform simple comparisons against values in the watch payload to determine whether or not to execute the watch actions.array_compare: compare an array of values in the watch payload to a given value to determine whether or not to execute the watch actions.script: use a script to determine whether or not to execute the watch actions.
If you omit the condition definition from a watch, the condition defaults to always.
When a condition is evaluated, it has full access to the watch execution context, including the watch payload (ctx.payload.*). The script, compare and array_compare conditions can use the payload data to determine whether or not the necessary conditions are met.
In addition to the watch wide condition, you can also configure conditions per action.