WARNING: Version 5.6 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 : truetoelasticsearch.yml. - Restart the Elasticsearch node.
-
Delete the
.watchesindex:DELETE .watches
-
Disable direct access to the
.watchesindex:- Stop the Elasticsearch node.
-
Remove
xpack.watcher.index.rest.direct_access : truefromelasticsearch.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.