-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metrics for kernel vulnerabilities #1046
Comments
Seems reasonable feature request. But parsing of this should go into procfs. |
See prometheus/node_exporter#1046 Signed-off-by: Ivan Babrou <[email protected]>
See prometheus/node_exporter#1046 Signed-off-by: Ivan Babrou <[email protected]>
Side note: spectre-meltdown-checker has a |
See prometheus/node_exporter#1046 Signed-off-by: Ivan Babrou <[email protected]>
See prometheus/node_exporter#1046 Signed-off-by: Ivan Babrou <[email protected]>
See prometheus/node_exporter#1046 Signed-off-by: Ivan Babrou <[email protected]>
See prometheus/node_exporter#1046 Signed-off-by: Ivan Babrou <[email protected]>
See prometheus/node_exporter#1046 Signed-off-by: Ivan Babrou <[email protected]>
hi i was looking to contribute and just wanted to know is this still a valid feature request? as i see the vulnerability parsing code was added to procfs https://github.com/prometheus/procfs/pull/190/files but the |
@palash25 Unless I missed some open PR, yeah a PR to add a collector for this here is very welcome! |
Newer kernels have this:
I wonder if we should export these as metrics in
node_exporter
:The text was updated successfully, but these errors were encountered: