- 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.
X-Pack Watcher Troubleshooting
editX-Pack Watcher Troubleshooting
editDynamic Mapping Error When Trying to Add a Watch
editIf you get the Dynamic Mapping is Disabled error when you try to add a watch,
verify that the index mappings for the .watches
index are available. You can
do that by submitting the following request:
GET .watches/_mapping
If the index mappings are missing, follow these steps to restore the correct mappings:
- Stop the Elasticsearch node.
-
Add
xpack.watcher.index.rest.direct_access : true
toelasticsearch.yml
. - Restart the Elasticsearch node.
-
Delete the
.watches
index:DELETE .watches
-
Disable direct access to the
.watches
index:- Stop the Elasticsearch node.
-
Remove
xpack.watcher.index.rest.direct_access : true
fromelasticsearch.yml
. - Restart the Elasticsearch node.
Unable to Send Email
editIf you get an authentication error indicating that you need to continue the sign-in process from a web browser when Watcher attempts to send email, you need to configure Gmail to Allow Less Secure Apps to access your account.
If you have two-step verification enabled for your email account, you must generate and use an App Specific password to send email from Watcher. For more information, see:
- Gmail: Sign in using App Passwords
- Outlook.com: App passwords and two-step verification
Watcher Not Responsive
editKeep in mind that there’s no built-in validation of scripts that you add to a watch. Buggy or deliberately malicious scripts can negatively impact Watcher performance. For example, if you add multiple watches with buggy script conditions in a short period of time, Watcher might be temporarily unable to process watches until the bad watches time out.
On this page