# Error when elasticsearch xpack.watcher.enabled:false

**URL:** <https://discuss.elastic.co/t/error-when-elasticsearch-xpack-watcher-enabled-false/161595>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [December 19, 2018, 9:15pm UTC](https://discuss.elastic.co/t/error-when-elasticsearch-xpack-watcher-enabled-false/161595 "2018-12-19T21:15:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![erikstephens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/erikstephens/32/5430_2.png) [@erikstephens](https://discuss.elastic.co/u/erikstephens)\
**Post date:** [December 19, 2018, 9:15pm UTC](https://discuss.elastic.co/t/error-when-elasticsearch-xpack-watcher-enabled-false/161595/1 "2018-12-19T21:15:48Z")

</div>

Using elasticsearch & metricbeat 6.5.3, I get this error when trying to ship `xpack.enabled:true` node\_stats to a 6.5.3 elasticsearch monitoring cluster:

> 2018-12-19T14:42:05.741Z ERROR node\_stats/data\_xpack.go:208 failure to apply node schema: 1 error: key `thread_pool.watcher` not found

Setting `xpack.watcher.enabled:true` in elasticsearch cluster config works around that issue. Should I be able to collect node\_stats when watch is disabled? Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 16, 2019, 9:15pm UTC](https://discuss.elastic.co/t/error-when-elasticsearch-xpack-watcher-enabled-false/161595/2 "2019-01-16T21:15:53Z")

</div>

Closed on January 16, 2019, 9:15pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.