A note for the community
- Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Problem
Firstly, thank you, I am loving Vector!
We have been using the 0.46.1-alpine image to collect host_metrics from within a container using PROCFS_ROOT and SYSFS_ROOT.
However I noticed that the network metrics looked a bit off, and indeed, it is reporting metrics on the network devices inside the container: lo and eth0 , not my AWS EC2 host, ens5, docker0 etc.
So it appears the env var isn't being respected for network stats
Configuration
host_metrics:
type: "host_metrics"
scrape_interval_secs: 5
# See: https://vector.dev/docs/reference/configuration/sources/host_metrics/#warnings
filesystem:
devices:
excludes: ["binfmt_misc"]
filesystems:
excludes: ["binfmt_misc"]
mountpoints:
excludes: ["*/proc/sys/fs/binfmt_misc"]
Version
vector 0.46.1 (aarch64-unknown-linux-musl 9a19e8a 2025-04-14 18:36:30.707862743)
Debug Output
Example Data
No response
Additional Context
No response
References
No response
A note for the community
Problem
Firstly, thank you, I am loving Vector!
We have been using the
0.46.1-alpineimage to collect host_metrics from within a container usingPROCFS_ROOTandSYSFS_ROOT.However I noticed that the network metrics looked a bit off, and indeed, it is reporting metrics on the network devices inside the container:
loandeth0, not my AWS EC2 host,ens5,docker0etc.So it appears the env var isn't being respected for network stats
Configuration
Version
vector 0.46.1 (aarch64-unknown-linux-musl 9a19e8a 2025-04-14 18:36:30.707862743)
Debug Output
Example Data
No response
Additional Context
No response
References
No response