Filebeat coredns module doesn't work with default coredns/docker logging

See Filebeat Autodiscovery for coredns in docker, what labels to use?

When using docker + hints, the filebeat coredns module silently fail sending any data.

Turns out the ingester tries to parse a leading "timestamp" that is not there (and fails silently...).

Are we doing anything wrong here or is this a bug of the coredns ingester?

Docker version 19.03.2, build 6a30dfc
ELK 7.3.2

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