-
Notifications
You must be signed in to change notification settings - Fork 89
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
0.6 issues #13
Comments
0.5.1 prints:
But then works. |
Hi @Sheridan! I'm having the same error as well
Please let me know if you need more details. Regards, |
Any update on this? |
I've run into this also - it appears that if you wait the configured minimum-collection interval, smartctl_exporter does write metrics to the http endpoint. But, as soon as you read before that (effectively) rate-limit, it panics, presumably because this line https://github.com/Sheridan/smartctl_exporter/blob/e27581d56ad80340fb076d3ce22cef337ed76679/readjson.go#L94 or the logic in https://github.com/Sheridan/smartctl_exporter/blob/e27581d56ad80340fb076d3ce22cef337ed76679/readjson.go#L79-L86 is wrong: Clearly, the first time you poll metrics, the tool should collect data... but it doesn't. |
Whats the default minimum-collection interval? Would blocking it from ready state in Kubernetes till then provide a workaround? I'm not sure prometheus honors a ready on a pod though. |
The default is 60s. I do think blocking reads would be a workaround, but pretty brittle. I'll try to see if I can fix this issue in a PR. |
Cool. Thanks. |
Done: #18 - hope this works for you too (: |
@Sheridan: Any change we can get a new release with this fix included? I'd also like to have the additional NVMe metrics ;-) |
Maybe development could continue over at https://github.com/azrdev/smartctl_exporter which just forked and merged a few of the outstanding patches. |
If I start it:
If I access it:
Back at the logs:
Manually running smartctl
The text was updated successfully, but these errors were encountered: