[ZBXNEXT-6954] New macros for debugging trigger expressions Created: 2021 Sep 28 Updated: 2024 Aug 30 Resolved: 2021 Nov 08 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Server (S) |
Affects Version/s: | None |
Fix Version/s: | 6.0.0alpha6, 6.0 (plan) |
Type: | New Feature Request | Priority: | Trivial |
Reporter: | Rostislav Palivoda | Assignee: | Dmitrijs Goloscapovs |
Resolution: | Fixed | Votes: | 4 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() ![]() |
||||||||||||
Issue Links: |
|
||||||||||||
Team: | |||||||||||||
Sprint: | Sprint 80 (Sep 2021), Sprint 81 (Oct 2021), Sprint 82 (Nov 2021) | ||||||||||||
Story Points: | 3 |
Description |
Currently, Zabbix doesn't provide good ways to debug trigger expression nor to put parts of trigger expression in alert messages in a convenient and unified way. There are some half-measures, such as {ITEM.VALUE}, default operational data or expression macros but these require additional efforts to deal with. Zabbix must provide a convenient way to access an evaluated trigger expression or its parts. |
Comments |
Comment by Alexei Vladishev [ 2021 Oct 18 ] |
This functionality is coming in Zabbix 6.0 soon. New macros {FUNCTION.VALUE<N>} and {TRIGGER.EXPRESSION.EXPLAIN} will be supported. |
Comment by Dmitrijs Goloscapovs [ 2021 Oct 22 ] |
Available in versions:
Documentation updated: |
Comment by Dimitri Bellini [ 2022 Jan 11 ] |
Hi Guys, Trigger Expression: (last(/test2/item.test1) + last(/test2/item.test2)) > {$MYMACRO} Event Name: Trg exp: {TRIGGER.EXPRESSION.EXPLAIN} - Trg fn1: {FUNCTION.VALUE1} - Trg fn2: {FUNCTION.VALUE2} The User MACRO is not expanded, is my fault? |
Comment by Dimitri Bellini [ 2022 Feb 11 ] |
Hi DevTeam, |