Something definitively looks off here. @exekias Do you have some ideas how the docker.service could get into the container.id value? It seems there are some events which have the correct values but other don't?
These are Linux conainers, while they are Docker based containers, in this case, system module can get info about any other platform. Perhaps we could do some matching to enrich this info with real Docker data, feel free to open a new issue in our repo
Also, have a look at our Docker module, probably it provides what you are seeking
If I open [Metricbeat Docker] Overview dashboard, Docker containers Names appears correct, unlike through [Metricbeat System] Containers overview dashboard, as it seems it's referring to wrong data (that is collected through system module instead of docker module).
Yep, that's what I was talking about. System dashboard is about Linux containers info, it's not targeting Docker, but any container runtime (LXC, for instance). That's why results are not as human readable as in Docker dashboard
Yet again, I guess Docker dashboard gives you everything you need?
Right, Docker Overview dashboard gives me containers IDs as it should, while System Containers overview dashboard instead of providing me with container related information, I get systemd metrics...
The question wasn't about Docker dashboard though, it was about System dashboard, part of that dashboard is Containers and yet what user gets is systemd, at very least it's misleading...
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.