# Fleet Ingest Docker Container Logs

**URL:** https://discuss.elastic.co/t/fleet-ingest-docker-container-logs/317416
**Category:** Elasticsearch
**Tags:** docker
**Created:** [October 25, 2022, 1:01pm UTC](https://discuss.elastic.co/t/fleet-ingest-docker-container-logs/317416 "2022-10-25T13:01:13Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![beerygaz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/beerygaz/32/53174_2.png) [@beerygaz](https://discuss.elastic.co/u/beerygaz)
#### Post date: [October 25, 2022, 1:01pm UTC](https://discuss.elastic.co/t/fleet-ingest-docker-container-logs/317416/1 "2022-10-25T13:01:13Z")

</div>

We'd like to try and use all the benefits of Fleet but also need to ingest _selected_ container logs. And add include/exclude regexes to these logs as some of them can be quite noisy and also badly formatted.

filebeat has a great method using the docker autodiscover, but other than using the very limited generic log integration in fleet I can't find anything else.

Has anyone else solved this? It it worth trying to bend fleet to our will or should we just revert to filebeat until fleet matures?

---

<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: [November 22, 2022, 1:02pm UTC](https://discuss.elastic.co/t/fleet-ingest-docker-container-logs/317416/2 "2022-11-22T13:02:02Z")

</div>

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