-
Problem report
-
Resolution: Fixed
-
Major
-
None
-
None
-
5.0.19
-
Sprint 84 (Jan 2022), Sprint 85 (Feb 2022), Sprint 86 (Mar 2022), Sprint 87 (Apr 2022), Sprint 88 (May 2022), Sprint 89 (Jun 2022), Sprint 90 (Jul 2022)
-
1
Evaluation period setting used in the trigger function "max" is wrong.
- Template
- Name: Template SAN NetApp FAS3220 SNMP
- https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/san/netapp_fas3220_snmp?at=refs%2Ftags%2F5.0.19
- MACRO Name: {$FAS3220.FS.TIME}
- default: 10G
- Trigger prototype
- Name: {#VSERVER}
{#FSNAME}: Disk space is too low (used over {$FAS3220.FS.PUSED.MAX.CRIT:"{#FSNAME}
"}% for {$FAS3220.FS.TIME:"
{#FSNAME}"})
– Expression: {Template SAN NetApp FAS3220 SNMP:fas3220.fs[dfPerCentKBytesCapacity, "{#VSERVER}{#FSNAME}"].max({$FAS3220.FS.TIME:"
{#FSNAME}"}){color}}>{$FAS3220.FS.PUSED.MAX.CRIT:" {#FSNAME}"} and {$FAS3220.FS.USE.PCT:"
{#FSNAME}"}=1
- Name: {#VSERVER}
{#FSNAME}: Disk space is too low (used over {$FAS3220.FS.PUSED.MAX.CRIT:"{#FSNAME}