# Filebeat: "memory leak" via filebeat.autodiscover and \>\>200.000 goroutines

**URL:** <https://discuss.elastic.co/t/filebeat-memory-leak-via-filebeat-autodiscover-and-200-000-goroutines/322082>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 28, 2022, 10:07am UTC](https://discuss.elastic.co/t/filebeat-memory-leak-via-filebeat-autodiscover-and-200-000-goroutines/322082 "2022-12-28T10:07:19Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)\
**Post date:** [January 3, 2023, 8:22am UTC](https://discuss.elastic.co/t/filebeat-memory-leak-via-filebeat-autodiscover-and-200-000-goroutines/322082/4 "2023-01-03T08:22:25Z")

</div>

Thanks! The memory heaps look familiar indeed.  
Can you also remove the

> [@HarryTuttle](#):
>
> `add_kubernetes_metadata`

processor?

The `kubernetes` provider is adding the metadata by default so you don't need the extra processor for this.

C.

---

_[View the full topic](https://discuss.elastic.co/t/filebeat-memory-leak-via-filebeat-autodiscover-and-200-000-goroutines/322082)._