-
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
Fixed an issue in the lustre input polgin with the jobstats only being reporeted for one job per storage target #5771
Conversation
I don't see your github username as having signed the CLA, could you do it again? One more favor if possible, I'd like to add a README for this plugin, would you be able to run:
|
I should have a CCLA through my employer, CSC - IT Center for Science LTD And I ran the command on both a metadata and object storage server in our active Lustre system. The outputs are quite long, ~1500 and ~800 lines, do you want it all? or should I create a representative subset of the output? |
Just a representative subset will be good. On the CLA, I might need you to sign the ICLA as well, but let me get back with you on that. |
Attached are representative outputs from one metadata (mds) and one object (oss) storage server. |
This change seems to have broken the ability to specify which proc files to process. In my case, I would like to disable the job_stats proc files and only process the others. Here's the relevant portion of my telegraf configuration:
When I use this config with Telegraf 1.11.2 (which includes merged this pull request), uncommenting the default inputs.lustre2 configuration (even without commenting out job_stats) produces an error:
When I revert to telegraf 1.10.4, which was prior to this merge, it works as expected:
Let me know if I should open an issue instead of commenting on this PR. |
@shawnahall71 This is probably related to the changes we made parsing TOML, similar to #5980. Could you open a new issue for this and we will address in 1.11.3. |
The current Lustre input plugin will only report jobstats for one job per storage target. This can be tested by running the included tests with the current version of the input plugin.
With this fix all jobs active on each storage target are recorded.
Required for all PRs: