-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
filesystem error count metric #3113
Comments
The node_exporter collector policy does not allow subprocess execution. It also does not allow for functions that require root privileges. This can probably be solved by reading from /sys/fs/ext4/. There is a work in progress to implement this in prometheus/procfs. |
right, running tune2fs seemed like an odd idea in the first place, i was hoping for something exactly like that. the PR you linked to has been merged, so we're getting close? :) i don't quite understand what it takes to percolate stuff from procfs into the node exporter itself, now we'd need a stub to call that |
Yes, lets track this in #3005 and close this here |
We are porting various alerts from Nagios to the prometheus ecosystem and we've found one check that is kind of useful in Nagios that seems to be missing from the node exporter. It's a check that looks at EXT filesystems with the
tune2fs -l
command and (basically) greps for theFS Error count
field.This should normally be zero but under certain circumstances (failing disk, filesystem bug, power outage), it will rise. running
fsck
on the filesystem will fix this (and, normally, after a power outage, a reboot will run fsck, but under certain circumstances, it might not fully do it).So I think the node exporter should do this. I've tried to find metrics about this in our node exporters and couldn't find anything under the
node_filesystem_*
namespace. There isnode_filesystem_readonly
and, according to this postnode_filesystem_device_error
(but I can't see that metric here), but neither of those are the same as the error count.Am I missing something or this is missing from the node exporter?
Here's a copy of the check, called
dsa-check-filesystems
here:The text was updated successfully, but these errors were encountered: