[ZBX-17340] Zabbix Trigger item value is incorrect on problem state Created: 2020 Feb 19  Updated: 2020 Feb 26  Resolved: 2020 Feb 26

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Andreas Drbal Assignee: Edgar Akhmetshin
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File zabbix-action-problem-config.png     PNG File zabbix-trigger-item-value-problem-incorrect.png    
Issue Links:
Duplicate
duplicates ZBXNEXT-3008 add macro {FUNCTION.VALUE<1-9>} to ca... Closed

 Description   

Steps to reproduce:

  1. Create a trigger expression for number of running processes for Linux. Example using average trigger function and value greater than 30 --> _ {[FQDN_OR_IP_HOST:proc.num[,,run]|https://zabbix.eng.citrite.net/items.php?form=update&itemid=397217].*avg(*5m*)*}

    >30_.

  2. Create a Zabbix Action and include the Zabbix Macro {ITEM.VALUE1}.
  3. When the trigger is fired the item value is incorrectly displayed.

This happens rarely but believe this might either be using the wrong macro or a potential bug.

I wanted to get clarity on this and whether this has been seen before.

I am using Zabbix version 4.0.15 on Debian 9 OS with partitioned (pg_partman) PostgreSQL v11.4 database.

Result: The Zabbix Item Value in the Action displays a wrong value; happens rarely. See attached screenshots.
Expected: To see the proper item value when the trigger fires.



 Comments   
Comment by Edgar Akhmetshin [ 2020 Feb 20 ]

Hello Andreas,

Could you please show raw values for the item used within trigger at mentioned time of a problem on the screenshot?

Regards,
Edgar

Comment by Andreas Drbal [ 2020 Feb 20 ]

Hello Edgar,

Thank you for your prompt reply.

Here are the raw values for the item used within the trigger mentioned:

$HOSTNAME: Number of running processes
2020-02-18 14:24:18 1582035858 1
2020-02-18 14:23:17 1582035797 2
2020-02-18 14:22:17 1582035737 1
2020-02-18 14:21:17 1582035677 1
2020-02-18 14:20:17 1582035617 8
2020-02-18 14:19:17 1582035557 95
2020-02-18 14:18:17 1582035497 59
2020-02-18 14:17:17 1582035437 5
2020-02-18 14:16:17 1582035377 3
2020-02-18 14:15:18 1582035318 3
2020-02-18 14:14:17 1582035257 1
2020-02-18 14:13:17 1582035197 1
2020-02-18 14:12:17 1582035137 1
2020-02-18 14:11:17 1582035077 1
2020-02-18 14:10:17 1582035017 1

At 14:21:21 the trigger fired with a value of 1.

We want to see the true error value when the trigger is fired. Are we using the wrong macro in the Zabbix Action? Instead of {ITEM.VALUE1} should we use {ITEM.VALUE} to get the true value of the problem when it actually goes off?

Let me know if you need any more information.

Thanks & Best Regards,
Andreas

Comment by Alexey Pustovalov [ 2020 Feb 20 ]

do you want to see real value of average for 5 latest minutes? ITEM.VALUE and ITEM.VALUE1 return just value which "fired" trigger.

Comment by Glebs Ivanovskis [ 2020 Feb 20 ]

doctorbal82, you may be interested in ZBXNEXT-3008.

Comment by Andreas Drbal [ 2020 Feb 20 ]

Alexey,

Yes, I would like to see the real value of the average for last 5 minutes that caused the trigger to fire.

I'm trying to understand why the PROBLEM value shows 1 for this trigger function. It was a bit confusing seeing that message with that value in a problem state.

Glebs,

Yes, I believe {FUNCTION.VALUE<1-9>} would suffice in this case.

Essentially we would like to see the actual value which is causing the problem in the media message which I believed to be ITEM.VALUE1.

Thanks & Best Regards,

Andreas

Comment by Edgar Akhmetshin [ 2020 Feb 26 ]

Hello Andreas,

Since 4.0 real value is not showed, please see for the reason and details: ZBXNEXT-4108, ZBXNEXT-4792, ZBXNEXT-4942. You need to use field 'operational data' starting since 4.4.

ZBXNEXT-3008 linked to the issue. Closing the issue as a duplicate.

Regards,
Edgar

Generated at Sat Apr 19 05:48:34 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.