- Watcher Reference for 2.x and 1.x:
- Introduction
- Getting Started
- Customizing Watches
- How Watcher Works
- Installing Watcher
- Administering Watcher
- Configuring Watcher to Send Email
- Configuring Watcher to Send Messages to HipChat
- Configuring Watcher to Send Messages to Slack
- Configuring Watcher to Send PagerDuty Events
- Integrating Watcher with Shield
- Integrating Watcher with Logstash
- Configuring the Default Throttle Period
- Configuring the Default HTTP Timeouts
- Configuring the Default Internal Operations Timeouts
- Getting Watcher Statistics
- Monitoring Watch Execution
- Managing Watches
- Example Watches
- Reference
- Managing Your License
- Limitations
- Troubleshooting
- Release Notes
Configuring the Default Internal Operations Timeouts
editConfiguring the Default Internal Operations Timeouts
editWhile Watcher is active, it often accesses different indices in Elasticsearch.
These can be internal indices used for its ongoing operation (such as the .watches
index where all the watches are stored) or as part of a watch execution via the
search
input, search
transform or the
index
actions.
To to ensure that Watcher’s workflow doesn’t hang on long running search or
indexing operations, these operations time out after a set period of time. You can
change the default timeouts in elasticsearch.yml
. The timeouts you can configure
are shown in the following table.
Name | Default | Description |
---|---|---|
|
30s |
The default timeout for all internal search operations. |
|
60s |
The default timeout for all internal index operations. |
|
120s |
The default timeout for all internal bulk operations. |