I recently upgraded from Zabbix 5.4 to 6.2 and I've read up about "Simple macros replaced by expression macros" in What's new in Zabbix 6.0.0.
I had Telegram alerts sending when updates were available on both Windows and Linux servers, which included the list of available items, but since the upgrade that broke and it just included the number of updates (which is the trigger expression).
I've tried various changes and added in other data and it all returns the number, am I going crazy or is this a bug?
Trigger Message (with test items)
With the output of that being:
But winupdates.critiallist contains the text "* Update for Microsoft Office 2016 (KB5002243) 64-Bit Edition" and 3 is the value of Winupdates.Critical (I've been manually setting it vis Zabbix Sender for testing) and it seems to just return the 3 for anything, I'm sure that's not the average cpu load too!
I hope that makes sense and someone can tell me what I'm doing wrong or if it looks like a bug.
Thanks!
I had Telegram alerts sending when updates were available on both Windows and Linux servers, which included the list of available items, but since the upgrade that broke and it just included the number of updates (which is the trigger expression).
I've tried various changes and added in other data and it all returns the number, am I going crazy or is this a bug?
Trigger Message (with test items)
Code:
Problem name: {TRIGGER.NAME}
Trigger Expression: {TRIGGER.EXPRESSION}
Trigger Value: {TRIGGER.VALUE}
{ITEM.VALUE1} ({ITEM.NAME1})
Processor load is: {?last(//system.cpu.load[,avg1])}
{?last(//Winupdates.CritialList)}
LUXDEVRS02 - Updates Available
Problem name: LUXDEVRS02 Updates Available
Trigger Expression: last(/LUXDEVRS02/Winupdates.Critical)>0
Trigger Value: 1
3 (Critical Updates)
Processor load is: 3
3
Problem name: LUXDEVRS02 Updates Available
Trigger Expression: last(/LUXDEVRS02/Winupdates.Critical)>0
Trigger Value: 1
3 (Critical Updates)
Processor load is: 3
3
I hope that makes sense and someone can tell me what I'm doing wrong or if it looks like a bug.
Thanks!