Currently, pcm-sensor-server only allows setting a custom port using the -p flag, but it always listens on all interfaces (0.0.0.0).
In some environments (e.g., multi-homed servers, containerized deployments, or restricted monitoring networks), it’s desirable to restrict the listening address — for example, to 127.0.0.1 or a specific management IP.
Feature Request:
Please consider adding an option such as:
--listen <ip>
or
--bind-address <ip>
so that users can control which interface pcm-sensor-server binds to.
Example usage:
pcm-sensor-server --listen 127.0.0.1 -p 9738
Rationale:
• Improves security by limiting exposure of the HTTP interface.
• Enables flexible deployment in Kubernetes, containers, and restricted monitoring networks.
• Aligns with common practices in other exporters (e.g., Prometheus node_exporter’s --web.listen-address flag).
Thank you for maintaining this excellent tool — it’s very useful for memory and CPU monitoring on Intel platforms.
Currently, pcm-sensor-server only allows setting a custom port using the -p flag, but it always listens on all interfaces (0.0.0.0).
In some environments (e.g., multi-homed servers, containerized deployments, or restricted monitoring networks), it’s desirable to restrict the listening address — for example, to 127.0.0.1 or a specific management IP.
Feature Request:
Please consider adding an option such as:
--listen <ip>or
--bind-address <ip>so that users can control which interface pcm-sensor-server binds to.
Example usage:
pcm-sensor-server --listen 127.0.0.1 -p 9738Rationale:
• Improves security by limiting exposure of the HTTP interface.
• Enables flexible deployment in Kubernetes, containers, and restricted monitoring networks.
• Aligns with common practices in other exporters (e.g., Prometheus node_exporter’s --web.listen-address flag).
Thank you for maintaining this excellent tool — it’s very useful for memory and CPU monitoring on Intel platforms.