Add_docker_metadata cannot process containers that already exited

Elastic Stack Beats
,
1

For the input type container if the log file is discovered after the container is stopped, the add_metadata_processor reports

{"file.name":"add_docker_metadata/add_docker_metadata.go","file.line":213},"message":"Container not found: cid=b8f04dcf8a6c222c234219d1116bea0be37c74432ad779d0dc4a8edc7072b056",
"service.name":"filebeat","ecs.version":"1.6.0"}

and no container metadata is added.
Is this a desired behavior or a bug?

2

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