# Docker input via autodiscovery not always json-decoding message

**URL:** https://discuss.elastic.co/t/docker-input-via-autodiscovery-not-always-json-decoding-message/157859
**Category:** Beats
**Tags:** filebeat
**Created:** [November 22, 2018, 10:41am UTC](https://discuss.elastic.co/t/docker-input-via-autodiscovery-not-always-json-decoding-message/157859 "2018-11-22T10:41:05Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![lifeofguenter](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lifeofguenter/32/17384_2.png) [@lifeofguenter](https://discuss.elastic.co/u/lifeofguenter)
#### Post date: [November 22, 2018, 3:33pm UTC](https://discuss.elastic.co/t/docker-input-via-autodiscovery-not-always-json-decoding-message/157859/4 "2018-11-22T15:33:48Z")

</div>

Right now it seems the `autodiscovery` plugin for `docker` is faulty. You can easily replicate by running filebeat as docker container and even natively.

There is no JSON error, but sometimes filebeat will json\_decode the `message` field and sometimes not. As shown in my example above.

It ties to this problem as well: [Docker + Persistent Registry = autodiscover failing](https://discuss.elastic.co/t/docker-persistent-registry-autodiscover-failing/157688/4)

Once I switch away from autodiscovery everything works perfectly.

---

_[View the full topic](https://discuss.elastic.co/t/docker-input-via-autodiscovery-not-always-json-decoding-message/157859)._