Open sergeysedoy97 opened 3 months ago
Pinging code owners for receiver/hostmetrics: @dmitryax @braydonk. See Adding Labels via Comments if you do not have permissions to add labels yourself.
Pinging code owners for extension/observer/hostobserver: @MovieStoreGuy. See Adding Labels via Comments if you do not have permissions to add labels yourself.
Maybe I am getting this wrong, but the hostmetrics receiver retrieves its data from the host. When using it inside a container, you may want to mount the hostfs as read-only into e.g. /hostfs
and use this as root_path
.
Maybe I am getting this wrong, but the hostmetrics receiver retrieves its data from the host. When using it inside a container, you may want to mount the hostfs as read-only into e.g.
/hostfs
and use this asroot_path
.
yes, receiver/hostmetrics can, but extension/observer/host can't
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
I don't follow. Please clarify your request.
Component(s)
No response
Describe the issue you're reporting
[receiver/hostmetrics] contains special config field
root_path
and supports gopsutil envs like HOST_PROCIs there any plan to add the container support for extension/observer/host?