[BUG] <title> hertzbeat-collector version:newest can not collect cpu info of Host Machine but only hertzbeat-collector's docker

[xiaoguolong]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

最新的版本hertzbeat部署到宿主机192.168.16.43机器，并通过在另外一台机192.168.16.173机器部署最新版本hertzbeat-collector，用的是linux脚本模板


上面收集到的信息是进去collector容器里面进程信息

Expected Behavior

收集到宿主机上的CPU信息

Steps To Reproduce

No response

Environment

HertzBeat version(s):

Debug logs

No response

Anything else?

No response

[zuobiao-zhou]

Since Docker containers operate in an isolated environment, each container has its own process space. If the container is configured to share the PID namespace (using --pid=host), it can access the host's PID namespace, but this reduces security. If possible, it is recommended to deploy the collector by downloading the hertzbeat-collector-xx.tar.gz package.

[xiaoguolong]

ok thanks . I have a try of deploy of tar

[xiaoguolong]

thank you . use your point of deploy ,it's ok

Since Docker containers operate in an isolated environment, each container has its own process space. If the container is configured to share the PID namespace (using --pid=host), it can access the host's PID namespace, but this reduces security. If possible, it is recommended to deploy the collector by downloading the hertzbeat-collector-xx.tar.gz package.

[zuobiao-zhou]

thank you . use your point of deploy ,it's ok

Since Docker containers operate in an isolated environment, each container has its own process space. If the container is configured to share the PID namespace (using --pid=host), it can access the host's PID namespace, but this reduces security. If possible, it is recommended to deploy the collector by downloading the hertzbeat-collector-xx.tar.gz package.

Thank you for your feedback. I had not fully considered this issue before. I will include relevant notes in the official documentation to better guide users.