claude-botandClaude Opus 5
24b2a0178d
The exporter reports all nine drives now, so the dashboard shows what it measures: a worst-wear stat in the status row, wear per drive over time, and a table of the failure-now signals — available spare, media errors, the critical warning bitfield, power-on time and written bytes. Every expression was run against the live TSDB and the label names read off real series rather than a README. That mattered: the exporter labels devices `nvme0` and carries model and serial on a separate `smartctl_device` info metric, so each query joins on (node, device) to pull the model in. A legend on the device name alone would compare different hardware across machines, which is the same trap the block-layer panels already avoid. Wear and damage are presented as different things because they are. The wear percentage is a budget the drive spends and says nothing about tomorrow; spare exhaustion, media errors and the critical warning mean something is wrong now. The caveats panel says so, and no longer claims endurance is missing — it was missing when that text was written and is not any more. Also fixes the OSD stat, which still rendered two identical numbers side by side. The commit that fixed it did not make it into #668 before that PR merged, so the panel went out in the state that prompted the complaint. It now shows OSDs down alone; up-but-out is a state rather than a fault and Ceph warns about it separately. Refs #549 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>