- X-Pack Reference for 6.0-6.2 and 5.x:
- Introduction
- Installing X-Pack
- Migrating to X-Pack
- Breaking Changes
- Securing Elasticsearch and Kibana
- Monitoring the Elastic Stack
- Alerting on Cluster and Index Events
- Reporting from Kibana
- Graphing Connections in Your Data
- Profiling your Queries and Aggregations
- Machine Learning in the Elastic Stack
- X-Pack Settings
- X-Pack APIs
- Info API
- Security APIs
- Watcher APIs
- Graph APIs
- Machine Learning APIs
- Close Jobs
- Create Datafeeds
- Create Jobs
- Delete Datafeeds
- Delete Jobs
- Delete Model Snapshots
- Flush Jobs
- Get Buckets
- Get Categories
- Get Datafeeds
- Get Datafeed Statistics
- Get Influencers
- Get Jobs
- Get Job Statistics
- Get Model Snapshots
- Get Records
- Open Jobs
- Post Data to Jobs
- Preview Datafeeds
- Revert Model Snapshots
- Start Datafeeds
- Stop Datafeeds
- Update Datafeeds
- Update Jobs
- Update Model Snapshots
- Validate Detectors
- Validate Jobs
- Definitions
- Troubleshooting
- Limitations
- License Management
- Release Notes
WARNING: Version 5.4 of the Elastic Stack has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Conditions
editConditions
editWhen a watch is triggered, its condition determines whether or not to execute the watch actions. Watcher supports the following condition types:
-
always: set the watch condition totrueso the watch actions are always executed. -
never: set the watch condition tofalseso 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 wehther 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.