- X-Pack Reference for 6.0-6.2 and 5.x:
- Introduction
- Setting Up X-Pack
- Breaking Changes
- X-Pack APIs
- Graphing Connections in Your Data
- Profiling your Queries and Aggregations
- Reporting from Kibana
- Securing the Elastic Stack
- Getting Started with Security
- How Security Works
- Setting Up User Authentication
- Configuring SAML Single-Sign-On on the Elastic Stack
- Configuring Role-based Access Control
- Auditing Security Events
- Encrypting Communications
- Restricting Connections with IP Filtering
- Cross Cluster Search, Tribe, Clients and Integrations
- Reference
- Monitoring the Elastic Stack
- Alerting on Cluster and Index Events
- Machine Learning in the Elastic Stack
- Troubleshooting
- Getting Help
- X-Pack security
- Can’t log in after upgrading to 6.2.4
- Some settings are not returned via the nodes settings API
- Authorization exceptions
- Users command fails due to extra arguments
- Users are frequently locked out of Active Directory
- Certificate verification fails for curl on Mac
- SSLHandshakeException causes connections to fail
- Common SSL/TLS exceptions
- Internal Server Error in Kibana
- Setup-passwords command fails due to connection failure
- X-Pack Watcher
- X-Pack monitoring
- X-Pack machine learning
- Limitations
- License Management
- Release Notes
WARNING: Version 6.2 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 totrue
so the watch actions are always executed. -
never
: set the watch condition 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 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.
In addition to the watch wide condition, you can also configure conditions per action.
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register now