# Change log level of add\_cloud\_metadata processor **URL:** \ **Category:** Elastic Agent\ **Tags:** filebeat, metricbeat\ **Created:** [January 30, 2024, 12:49pm UTC](https://discuss.elastic.co/t/change-log-level-of-add-cloud-metadata-processor/352087 "2024-01-30T12:49:02Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Alphayeeeet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alphayeeeet/32/126382_2.png) [@Alphayeeeet](https://discuss.elastic.co/u/Alphayeeeet)\ **Post date:** [January 30, 2024, 12:49pm UTC](https://discuss.elastic.co/t/change-log-level-of-add-cloud-metadata-processor/352087/1 "2024-01-30T12:49:02Z")
Elastic Agent version: 8.11.3 The add\_cloud\_metadata processor is used in filebeat/metricbeat by default. When deploying non-cloud Elastic Agent on own premises, the processor tries to add the metadata and fails with error. The log level of this failure should be reduced to info or if it is necessary warning, because it does not represent a serious failure: ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/d/0dc571f20170574c90ed1c9f07d246a4b31f1569.png) ---
**Author:** ![yago82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yago82/32/97755_2.png) [@yago82](https://discuss.elastic.co/u/yago82)\ **Post date:** [January 30, 2024, 1:07pm UTC](https://discuss.elastic.co/t/change-log-level-of-add-cloud-metadata-processor/352087/2 "2024-01-30T13:07:08Z")
> [@Alphayeeeet](#): > > Elastic Agent version: 8.11.3 > > The add\_cloud\_metadata processor is used in filebeat/metricbeat by default. When deploying non-cloud Elastic Agent on own premises, the processor tries to add the metadata and fails with error. The log level of this failure should be reduced to info or if it is necessary warning, because it does not represent a serious failure: Hi, you can remove or comment out the `add_cloud_metadata` processor in your Filebeat and Metricbeat configurations Regards ---
**Author:** ![Alphayeeeet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alphayeeeet/32/126382_2.png) [@Alphayeeeet](https://discuss.elastic.co/u/Alphayeeeet)\ **Post date:** [January 30, 2024, 1:09pm UTC](https://discuss.elastic.co/t/change-log-level-of-add-cloud-metadata-processor/352087/3 "2024-01-30T13:09:49Z")
Thank you for the reply. I am using Fleet managed Elastic Agent with integration as my configuration. Therefore I cannot disable the add\_cloud\_metadata processor in default, because the integrations enable it by default and there is (as far as I know) no definition, where I could comment it out. If you have any precise advice, how to disable the processor on Fleet managed Elastic Agent, I would really appreciate it. ---
**Author:** ![yago82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yago82/32/97755_2.png) [@yago82](https://discuss.elastic.co/u/yago82)\ **Post date:** [January 30, 2024, 1:12pm UTC](https://discuss.elastic.co/t/change-log-level-of-add-cloud-metadata-processor/352087/4 "2024-01-30T13:12:42Z")
Hi, probably you might consider using standalone Elastic Agents (not managed by Fleet) if you need more granular control over the configuration, including the ability to disable specific processors. Regards ---
**Author:** ![Alphayeeeet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alphayeeeet/32/126382_2.png) [@Alphayeeeet](https://discuss.elastic.co/u/Alphayeeeet)\ **Post date:** [January 30, 2024, 1:16pm UTC](https://discuss.elastic.co/t/change-log-level-of-add-cloud-metadata-processor/352087/5 "2024-01-30T13:16:14Z")
Hi, It doesn't bother me that much, but as I mentioned above, I think it should be implemented, that the log level is changed or the message suppressed when deploying in a self managed (non-cloud) environment. Regards 🙂 ---
**Author:** ![Alphayeeeet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alphayeeeet/32/126382_2.png) [@Alphayeeeet](https://discuss.elastic.co/u/Alphayeeeet)\ **Post date:** [February 15, 2024, 4:16pm UTC](https://discuss.elastic.co/t/change-log-level-of-add-cloud-metadata-processor/352087/6 "2024-02-15T16:16:32Z")
still relevant ---
**Author:** ![Alphayeeeet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alphayeeeet/32/126382_2.png) [@Alphayeeeet](https://discuss.elastic.co/u/Alphayeeeet)\ **Post date:** [March 12, 2024, 2:08pm UTC](https://discuss.elastic.co/t/change-log-level-of-add-cloud-metadata-processor/352087/7 "2024-03-12T14:08:29Z")
still relevant ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 9, 2024, 2:08pm UTC](https://discuss.elastic.co/t/change-log-level-of-add-cloud-metadata-processor/352087/8 "2024-04-09T14:08:41Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.