Currently, the official template "SMART by Zabbix agent 2" uses global macros for temperature triggers (e.g., {}{$SMART.TEMPERATURE.MAX.CRIT}{}). This approach applies the same threshold to all discovered disks.

Different disk technologies have different operating temperatures. For example, NVMe drives typically run much hotter than standard HDDs. Using a single global threshold often leads to false positives for NVMe drives or loose monitoring for HDDs.

Please update the trigger prototypes to use user macros with context.
Change: last(/host/key) > {$SMART.TEMPERATURE.MAX.CRIT}
To: {{last(/host/key) > {$SMART.TEMPERATURE.MAX.CRIT:"

{#NAME}

"}}}

This would allow administrators to define specific overrides on the host level, for example:

• {$SMART.TEMPERATURE.MAX.CRIT} = 60 (Global default)
• {$SMART.TEMPERATURE.MAX.CRIT:"/dev/nvme0n1"} = 75 (Specific for NVMe)

Discussion on Zabbix Forum: https://www.zabbix.com/forum/zabbix-suggestions-and-feedback/415662-discussion-thread-for-official-zabbix-smart-disk-monitoring/page10#post506951