smartctl_exporter icon indicating copy to clipboard operation
smartctl_exporter copied to clipboard

Export smartctl statistics to prometheus

Results 51 smartctl_exporter issues
Sort by recently updated
recently updated
newest added

In line with [Prometheus][1], I'd like to rename the default branch from `master` to `main`. This will be done _after_ all PRs are accepted/closed. People who forked the repo may...

enhancement

Fake data can be fed to `smartctl_exporter` by using the `--smartctl.fake-data` flag which reads the JSON from `./testdata` for devices. `readSMARTctlDevices()` exec's `smartctl --json --scan` to get the list of...

Currently the smartctl exporter only attaches the `device` label to all metrics except `smartctl_device`. This was introduced in #83. This can unfortunately lead to issues, since device nodes are not...

The `--xall` parameter was removed in https://github.com/prometheus-community/smartctl_exporter/commit/e88442081c18fcac9025e4d806786e12c791cc10, but no `--log` parameter was added. Hence, the `smartctl_device_num_err_log_entries`, `smartctl_device_error_log_count`, `smartctl_device_self_test_log_count`, and `smartctl_device_self_test_log_error_count` metrics stay empty as the smartctl does not report the...

The last multi-arch build was `v0.7.0`. Is there any reason not to re-enable it?

bug

Currently, we only check whether `smart_status.passed` is true. If it's false, then assume SMART did not pass. However, there's another possibility that the device doesn't support SMART at all. https://github.com/prometheus-community/smartctl_exporter/blob/7482daf69a4e93eafa62479a30d3c2ae39fb7991/smartctl.go#L462...

PR #188 added lots of test files containing `smartctl` output. To test PRs such as #205, it would be nice to have the output of `smartctl --scan --json`. Either add...

did anyone create a dashboard for this exporter? I am currently rewriting [this dashboard](https://grafana.com/grafana/dashboards/10664) for this exporter.

https://github.com/prometheus-community/smartctl_exporter/pull/131/files#diff-c249026c4aeb110469ab01c3170ce12c5a292612584702fd378d42a1c868a686 This introduced a bug where smartctl return code is 4 instead of 0 if any messages were present in the call. ``` "messages": [ { "string": "Read 1 entries...

I manage a Linux box with around 20-25 HDDs. Some of these disks are faster to reply to smartctl, others are pretty slow, taking around 1-2 seconds. Setting the scrape...