Summary

smart.disk.get[] currently exposes only a subset of the standard NVMe SMART / Health Information available through smartctl.

For example, smartctl reports:

{{Available Spare: 100%
Available Spare Threshold: 5%
Percentage Used: 27%
Data Units Read: 33,600,687
Data Units Written: 47,705,239
Power Cycles: 58
Power On Hours: 4,354
Unsafe Shutdowns: 4
Media and Data Integrity Errors: 0
Error Information Log Entries: 48
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0}}

while smart.disk.get[] only exposes:

{{

{ "critical_warning": 0, "media_errors": 0, "percentage_used": 27, "power_on_time": 4354, "temperature": 36 }

}}

It would be useful to additionally expose at least:

• available_spare

• available_spare_threshold

• data_units_read

• data_units_written

• power_cycles

• unsafe_shutdowns

• error_information_log_entries

• warning_temperature_time

• critical_temperature_time

and add corresponding items to the official SMART by Zabbix agent 2 template.

For cumulative counters such as unsafe_shutdowns and error_information_log_entries, triggers should preferably detect an increase/change instead of triggering on an already existing non-zero value.