# See autodiscovery generated configs

**URL:** <https://discuss.elastic.co/t/see-autodiscovery-generated-configs/275567>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 10, 2021, 12:39pm UTC](https://discuss.elastic.co/t/see-autodiscovery-generated-configs/275567 "2021-06-10T12:39:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Moshe\_Avni](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/moshe_avni/32/90121_2.png) [@Moshe\_Avni](https://discuss.elastic.co/u/Moshe_Avni)\
**Post date:** [June 10, 2021, 12:39pm UTC](https://discuss.elastic.co/t/see-autodiscovery-generated-configs/275567/1 "2021-06-10T12:39:59Z")

</div>

Hi, on the [autodiscovery docs](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-autodiscover.html#_providers), it says:

> On start, Filebeat will scan existing containers and launch the proper configs for them.

Is there a way to see the 'launched' configurations to debug if something is wrong with them?  
Right now it's hard to debug autodiscovery errros.

---

<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:** [July 8, 2021, 2:40pm UTC](https://discuss.elastic.co/t/see-autodiscovery-generated-configs/275567/2 "2021-07-08T14:40:33Z")

</div>

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