Closed fchiorascu closed 6 years ago
Process per CPU, MEMORY as consumption.
I'm not sure what this means.
Network Interface status UP/DOWN,speed link.
This is already covered by https://github.com/prometheus/node_exporter/issues/794.
Threads.
Can you be more specific? Are you sure this is not covered by https://github.com/prometheus/node_exporter/pull/950?
Process per CPU, MEMORY as consumption.
I'm not sure what this means. This means: Running Processes by Memory and CPU Usage in Linux # ps -eo pid,ppid,cmd,%mem,%cpu --sort=-%mem | head
Network Interface status UP/DOWN,speed link.
This is already covered by #794. This is only applied to "bonding" or general for network?
Threads.
Can you be more specific? Are you sure this is not covered by #950? I think is covered, will be in the next release of node_exporter 0.17?
Thank you.
Per-process metrics are out of scope for the node exporter. I would look into cAdvisor or the process_exporter.
Even better would be to add a client library in your applications. This way you can directly measure each process. The Prometheus client libraries include a number of automatic metrics for process memory and CPU information.
/sys/class/net/*
, I've updated the title to make that more clear.Thank you @SuperQ this sounds great. Have a great day.