# Cannot disable "xpack.monitoring.collection.enabled" setting **URL:** \ **Category:** Elasticsearch\ **Created:** [April 14, 2024, 11:25am UTC](https://discuss.elastic.co/t/cannot-disable-xpack-monitoring-collection-enabled-setting/357358 "2024-04-14T11:25:31Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![SamehSaeed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samehsaeed/32/145262_2.png) [@SamehSaeed](https://discuss.elastic.co/u/SamehSaeed)\ **Post date:** [April 14, 2024, 11:25am UTC](https://discuss.elastic.co/t/cannot-disable-xpack-monitoring-collection-enabled-setting/357358/1 "2024-04-14T11:25:31Z")
Hello, I'm using Kibana upgrade assistant to fix a vulnerability issue, the problem is I need to resolve all warnings, one warning that i couldn't fix is this : `the setting [xpack.monitoring.collection.enabled] is currently set to [true], remove this setting (nodes impacted: [SCPRWUWS05])` I tried setting "xpack.monitoring.collection.enabled" to false in elasticsearch.yml file, but nothing was changed. How do i disable this? ---
**Author:** ![SamehSaeed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samehsaeed/32/145262_2.png) [@SamehSaeed](https://discuss.elastic.co/u/SamehSaeed)\ **Post date:** [April 15, 2024, 11:10am UTC](https://discuss.elastic.co/t/cannot-disable-xpack-monitoring-collection-enabled-setting/357358/2 "2024-04-15T11:10:08Z")
After using metricbeat and disabled self monitoring for elasticsearch & kibana, 1 more warning popped up : ```auto setting [xpack.monitoring.elasticsearch.collection.enabled] is deprecated and will be removed after 8.0 ``` ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/0/90cb9c0bcdb99115e475fb8761523f5dd9c090a4.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/6/76d870f2edb43bd2c9e6c163fedfcc9cdbb449ab.png) Is there any way to skip these warnings? Can I install the new version and import the old snapshot? ---
**Author:** ![SamehSaeed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samehsaeed/32/145262_2.png) [@SamehSaeed](https://discuss.elastic.co/u/SamehSaeed)\ **Post date:** [April 21, 2024, 6:57am UTC](https://discuss.elastic.co/t/cannot-disable-xpack-monitoring-collection-enabled-setting/357358/3 "2024-04-21T06:57:54Z")
Found the solution, just need to set these 2 settings to "null" in kibana dev tools : ```auto PUT /_cluster/settings { "xpack.monitoring.collection.enabled": null } PUT /_cluster/settings { "xpack.monitoring.elasticsearch.collection.enabled": null } ``` ---
**Author:** ![archon810](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/archon810/32/67033_2.png) [@archon810](https://discuss.elastic.co/u/archon810)\ **Post date:** [October 4, 2025, 6:52am UTC](https://discuss.elastic.co/t/cannot-disable-xpack-monitoring-collection-enabled-setting/357358/4 "2025-10-04T06:52:11Z")
Hmm. Both of those commands return this on 9.1.4: ```auto { "error": { "root_cause": [ { "type": "action_request_validation_exception", "reason": "Validation Failed: 1: no settings to update;" } ], "type": "action_request_validation_exception", "reason": "Validation Failed: 1: no settings to update;" }, "status": 400 } ``` Even though: ```auto { "persistent": { "xpack": { "monitoring": { "collection": { "enabled": "true" } } } }, "transient": {} } ``` ---
**Author:** ![SamehSaeed](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/samehsaeed/32/145262_2.png) [@SamehSaeed](https://discuss.elastic.co/u/SamehSaeed)\ **Post date:** [October 5, 2025, 6:43am UTC](https://discuss.elastic.co/t/cannot-disable-xpack-monitoring-collection-enabled-setting/357358/5 "2025-10-05T06:43:18Z")
Hello @archon810 , These settings are probably removed now (I was using ELK stack 8.10 back then), they have been deprecated long ago. Check this URL : > **[Monitoring settings in Elasticsearch | Reference](https://www.elastic.co/docs/reference/elasticsearch/configuration-reference/monitoring-settings)** > > By default, Elasticsearch monitoring features are enabled but data collection is disabled. To enable data collection, use the xpack.monitoring.collection.enabled... ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/e/0ee9cbcba2739a64ed73215386b6c9ed8982b390.png) ---
**Author:** ![archon810](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/archon810/32/67033_2.png) [@archon810](https://discuss.elastic.co/u/archon810)\ **Post date:** [October 5, 2025, 5:14pm UTC](https://discuss.elastic.co/t/cannot-disable-xpack-monitoring-collection-enabled-setting/357358/6 "2025-10-05T17:14:15Z")
You’re right, it’s deprecated, which is why I’m trying to get rid of the entry in `GET /_cluster/settings` which currently returns in 9.1.4: ```auto { "persistent": { "xpack": { "monitoring": { "collection": { "enabled": "true" } } } }, "transient": {} } ``` I don’t want to keep a confusing/deprecated setting entry in there. ---
**Author:** ![K4zp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/k4zp/32/136367_2.png) [@K4zp](https://discuss.elastic.co/u/K4zp)\ **Post date:** [June 17, 2026, 7:50am UTC](https://discuss.elastic.co/t/cannot-disable-xpack-monitoring-collection-enabled-setting/357358/7 "2026-06-17T07:50:56Z")
Depending on the response to `GET _cluster/settings` you need to add persistent or transient. In my case the following command removed the setting. This also made the Upgrade Assistant happy and it went from `Warning` to `No issues` ```auto PUT /_cluster/settings { "persistent": { "xpack.monitoring.collection.enabled": null } } ```