- 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
From version 5.0 onward, Watcher is part of X-Pack. For more information, see
Alerting on cluster and index events.
Watcher Settings
editWatcher Settings
editYou can configure the following settings for Watcher in the
elasticsearch.yml
configuration file.
-
watcher.http.proxy.host
- Specifies the address of the proxy server to use to connect to HTTP services.
-
watcher.http.proxy.port
- Specifies the port number to use to connect to the proxy server.
-
watcher.http.ssl.keystore.path
-
The SSl keystore path to use for PKI-based authentication. If not specified,
the Watcher HTTP client falls back to the value of the
shield.ssl.keystore.path
setting. -
watcher.http.ssl.keystore.password
-
The SSl keystore password to use for PKI-based authentication. If not specified,
the Watcher HTTP client falls back to the value of the
shield.ssl.keystore.password
setting. -
watcher.http.ssl.truststore.path
-
The SSl truststore path to use for specifying the certificates and certificate authorities to trust.
If not specified, the Watcher HTTP client falls back to the value of the
shield.ssl.truststore.path
setting. -
watcher.http.ssl.truststore.password
-
The SSl truststore password to use for access to the truststore. If not specified,
the Watcher HTTP client falls back to the value of the
shield.ssl.truststore.password
setting. -
watcher.http.ssl.verification_mode
-
Specifies whether the HTTP client should verify hostnames or certificates only. The default is
full
, which verifies both the certificate and server’s hostname. The only other valid option iscertificate
, which skips hostname verification but still requires the server’s certificate to be trusted.
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register nowWas this helpful?
Thank you for your feedback.