[ZBX-20473] Trigger error "invalid first parameter" for FAS3220 Template Created: 2022 Jan 24  Updated: 2024 Apr 10  Resolved: 2022 Jul 10

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: None
Fix Version/s: 5.0.26rc1, 6.0.7rc1, 6.2.1rc1, 6.4.0alpha1, 6.4 (plan)

Type: Problem report Priority: Major
Reporter: Hayato Watanabe Assignee: Denis Rasikhov
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

5.0.19

Attachments: PNG File Screenshot_254.png    
Team: Team INT
Sprint: 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)
Story Points: 1

 Description   

Evaluation period setting used in the trigger function "max" is wrong.

  • Template
  • 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

 Comments   
Comment by Denis Rasikhov [ 2022 Jun 30 ]

Fixed in:

Comment by Gabriel W PC [ 2022 Jul 09 ]

OK, every who have the same issue, just like me a few hours ago, just replace the Macro's value {$FAS3220.FS.TIME} from 10G to 10m and problem solved.

It must be looking like this, save changes and started working. =)

Generated at Wed Jul 16 12:32:12 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.