-
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
Lustre2 plugin #86
Lustre2 plugin #86
Conversation
The configuration allows users to override the /proc/ files scanned for data, since that has been known to change with lustre versions.
Oh, one other remark: it uses ReadLines from system/ps/common/, to avoid code duplication. I'm unsure if that would be considered safe behaviour. It's tempting to move those common plugin utilities up a level for use across all plugins. |
1dd560c
to
d09e5f3
Compare
Thanks for the contribution! Don't worry about the ReadLines piece, I will be refactoring all of that code to just use the external gopsutil library anyways |
@srfraser I can merge this once you've fixed the branch conflicts |
…stre2-plugin Conflicts: testutil/accumulator.go
@sparrc Done - thank you! |
Lustre2 plugin
Lustre is a high performance cluster filesystem (http://lustre.org), used in HPC environments. Usefully, it makes data available in /proc, so here is a plugin to read those /proc files.
Lustre 2.x stores them in a different location to Lustre 1.x, hence the versioned plugin information. The configuration file allows those locations to be overridden for future proofing, and to make testing easier.
One modification that may be necessary until cross-measurement mathematics is enabled is to store read_bytes and read_calls (and write_*) in the same measurement to get mean bytes per call metrics.