How to have different triggers on same SNMP discovery?

[compuj85]

Hello,

I'm using the template Supermicro Aten by SNMP to monitor many Supermicro servers in Zabbix 7.4.3.

This template does an SNMP discovery of all temperature sensors with this OID:

discovery[{#SNMPVALUE},1.3.6.1.4.1.21317.1.3.1.2,{#SENSOR_DE SCR},1.3.6.1.4.1.21317.1.3.1.13]

This discovers CPU temperatures, NIC temperatures, and GPU temperatures. The problem is that all of these use the same {$TEMP_WARN} and {$TEMP_CRIT} macro; and the GPUs can run much hotter than the CPU or NIC - around 80*C in some cases. To avoid alarms I've had to set {$TEMP_CRIT} very high, higher than I would like for the CPUs.

Is there a way to have a different limit based on the item name? In the Discovery Rule Override I think I can change the severity based on {#SENSOR_DESCR}, but not the trigger value. Items get names like CPU 1 Temp, GPU1 Temp, etc.

Thanks,

-Jason

[PSklyar]

Hey hey !
I can advise you to configure discovery rule overrides
Create custom macros for each sensor type, like :
{$TEMP.CPU.WARN} = 70
{$TEMP.CPU.CRIT} = 80
{$TEMP.GPU.WARN} = 85
{$TEMP.GPU.CRIT} = 95
https://blog.zabbix.com/extend-your-...errides/15496/
Then create 3 overrides, cpu temp trigger / gpu temp trigger and nic

[compuj85]

...
Then create 3 overrides, cpu temp trigger / gpu temp trigger and nic

That's where I'm confused - I see where the override can change the severity, add tags, prevent the trigger creation... but not use different macros.

Thanks,

-J

[compuj85]

I was able to solve this with regex in the macro (notes here: https://www.zabbix.com/documentation...cros_context):

{$TEMP_CRIT} 75
{$TEMP_CRIT:regex:".*10G.*"} 80
{$TEMP_CRIT:regex:".*NIC.*"} 80
{$TEMP_CRIT:regex:"GPU.*"} 90

Thanks,

-J