- 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.
Always Condition
editAlways Condition
editUse the always
condition to set the condition to true
. This forces the watch
actions to be executed unless they are throttled.
The always
condition enables you to perform watch actions on a fixed schedule,
such as, "Every Friday at noon, send a status report email to
sys.admin@example.com."
Using the Always Condition
editThis is the default if you omit the condition definition from a watch.
There are no attributes to specify for the always
condition. To explicitly
use this condition, specify the condition type and associate it with an empty
object:
"condition" : { "always" : {} }
On this page