Setup: docker logs are not in the default folder "/var/lib/docker/containers//-json.log" but in "/home/var/docker/data/containers//-json.log" Filebeat works just fine and pushes docker logs into elasticsearch Problem: "docker.container.id" always says "containers" instead of the actual ids This…

alright, my bad. Checking the source more closely, you can actually inject parameters for this using not sourceindex but match_source_index, like you can change the host. type: log enabled: true paths: - /home/var/docker/data/containers/*/*-json.log scan_frequency: 10s processors: - …

Add_docker_metadata failing to get container id if logs are in different path

Elastic Stack Beats

somelifeDev (Gregory) August 8, 2018, 9:10am 4

Ok, I found the problem

It's HARDCODED that ids should be in the 5th position of the path..

see github

Topic		Replies	Views
Filebeats to correctly propagate Docker container information into Elasticsearc Beats docker , filebeat	2	459	May 30, 2019
Filebeat doesn't accept logs with container name Beats docker , filebeat	4	727	September 2, 2020
Missing docker metadata in filebeat Beats docker , filebeat	5	1397	June 16, 2020
Add docker metadata not working even after trying all possible combinations Beats filebeat	9	1260	December 25, 2018
Filebeat add docker metada fail Beats filebeat	2	396	August 18, 2020

Add_docker_metadata failing to get container id if logs are in different path

Related topics