16f7122d31
While the CPU vulnerabilities collector has been added in https://github.com/prometheus/node_exporter/pull/2721 , it's currently not including information regarding the mitigation strategy used for a given vulnerability. This information can be quite valuable, as often times different mitigation strategies come with a different performance impact. This commit adds a third label to the cpu_vulnerabilities_info metric, to include the "mitigation" used for a given vulnerability - if a given vulnerability is not affecting a node or the node is still vulnerable, the mitigation is expected to be empty. Signed-off-by: João Lima <jlima@cloudflare.com> |
||
|---|---|---|
| .. | ||
| ethtool | ||
| proc | ||
| qdisc | ||
| textfile | ||
| usr/lib | ||
| wifi | ||
| e2e-64k-page-output.txt | ||
| e2e-output.txt | ||
| ip_vs_result.txt | ||
| ip_vs_result_lbs_local_address_local_port.txt | ||
| ip_vs_result_lbs_local_port.txt | ||
| ip_vs_result_lbs_none.txt | ||
| sys.ttar | ||
| udev.ttar | ||