-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Track system-wide file descriptor usage #2597
Comments
Seems useful. I have been more interested in my per user limits, because I always seem to hit them first, but these are important too. I think these are more advanced metrics, so I'm inclined to put them in a new measurement. That way they are not turned on as part of the system measurement and there is no confusion about how to turn them on. It might still be possible for this measurement to have available metrics for more than one operating system though, so long as they don't conflict. |
Doesn't the procstat plugin track limits? Haven't really used it for much, so not sure. If not then I would think it should. In any case, any preferences/ideas on the input & measurement names? |
Yeah, it has number of file descriptors, I don't know of a better way to get fd per user other than summing them up by process, so I guess running procstat with user is good. I'm thinking |
I'm not sure what you mean by per-user. There is no per-user file descriptor limit. Only per-process, and system wide. As far as the name, I'm fine with that sort of scheme. But we've recently decommissioned all our FreeBSD hosts, or I would have objected much more vocally, as having to select this field from 2 different measurements would be a pain. Will start on this. Should be an easy implementation. |
Oh, I always thought |
Implemented in #2609 |
Feature Request
Proposal:
Telegraf should report on system-wide (not process-level) file descriptor usage & limit.
Current behavior:
Does not do.
Desired behavior:
Do.
Use case: [Why is this important (helps with prioritizing requests)]
If the number of file descriptors used reaches the max, any attempts by applications to open any new ones will fail. Thus it is an important statistic to monitor.
Now my uncertainty is whether we should monitor additional stuff, and where it should go.
There are a bunch of metrics that are reported along side the file descriptor usage metric: https://www.kernel.org/doc/Documentation/sysctl/fs.txt (everything with -max, -nr, & -state suffixes). Given the number of potential metrics, it might make sense to put these in a new measurement, such as
linux_sysctl_fs
.The main argument against this is that other operating systems, such as FreeBSD, also have a system-wide max file descriptor count, but not some of the other stuff. In which case for consistency across platforms, it makes sense to use the
system
measurement.The text was updated successfully, but these errors were encountered: