- X-Pack Reference for 6.0-6.2 and 5.x:
- Introduction
- Installing X-Pack
- Migrating to X-Pack
- Breaking Changes
- Breaking Changes in 5.5.2
- Breaking Changes in 5.5.0
- Breaking Changes in 5.3
- Breaking Changes in 5.2
- Breaking Changes in 5.0
- Breaking Changes in Shield 2.4.2
- Breaking Changes in Reporting 2.4.1
- Breaking Changes in Shield 2.4.0
- Breaking Changes in Shield 2.1.0
- Breaking Changes in Shield 2.0.1
- Breaking Changes in 2.0.0
- Breaking Changes in Shield 1.3.0
- X-Pack Settings
- X-Pack APIs
- Graphing Connections in Your Data
- Profiling your Queries and Aggregations
- Reporting from Kibana
- Securing Elasticsearch and Kibana
- Monitoring the Elastic Stack
- Alerting on Cluster and Index Events
- Machine Learning in the Elastic Stack
- Troubleshooting
- Limitations
- License Management
- Release Notes
WARNING: Version 5.5 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.
Inputs
edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.
Inputs
editWhen a watch is triggered, its input loads data into the execution context. This payload is accessible during the subsequent watch execution phases. For example, you can base a watch’s condition on the data loaded by its input.
Watcher supports four input types:
If you don’t define an input for a watch, an empty payload is loaded into the execution context.
Was this helpful?
Thank you for your feedback.