-
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
Add setting to enable caching in ipmitool #8335
Add setting to enable caching in ipmitool #8335
Conversation
@reimda I am under the impression your requested changes marked the checks failed. Can you tell me whats wrong about it now? |
Moreover, please rebase on master. |
772154c
to
d2015d3
Compare
rebased and formatted as requested. Please add hacktoberfest-accepted label on merge |
@reimda do you still see something? |
@DEvil0000 PR still needs to be rebased. |
dc0585f
to
43c5fd2
Compare
@zak-pawel rebase done. |
(cherry picked from commit 358633b)
I had the issue that ipmi data was reported with gaps on a 30s interval on HP G10 servers (latest firmware).
The gaps where due to the ipmitool command was not always finishing within the 20s timeout. Even changeing the timeout to 30s was not always giving it enough time to respond.
ipmi-sensors from freeipmi tools which is used in some prometheus ipmi exporters is running way faster but does not provide all information I needed.
At some point I just realized there is a cache option for ipmitool. Using this option speeds the tool up by something between 3x and 6x for most of my runs so it holds the deadline given by timeout and I can record the data not even in 30s intervals but also now in 15s intervals.
In case you merge this or agree with it, I would appreciate a hacktoberfest-accepted label.