When starting telemd as container or pod, it currently ignores to fetch cgroup network metrics of the daemon itself.
The reason is that due to the introduction of a custom /proc path, the daemon's PID is most likely not available anymore.
Solution: implement a way, such that the via env variable set /proc mount is parsed, as well as the /proc path in the container.
When starting telemd as container or pod, it currently ignores to fetch cgroup network metrics of the daemon itself.
The reason is that due to the introduction of a custom /proc path, the daemon's PID is most likely not available anymore.
Solution: implement a way, such that the via env variable set /proc mount is parsed, as well as the /proc path in the container.