trigger_ifcontrol actual.png
trigger_ifcontrol.png
[ZBX-17971] Link down trigger description problem Created: 2020 Jun 25 Updated: 2020 Jun 28 |
|
| Status: | Open |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Templates (T) |
| Affects Version/s: | 5.0.0 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | Evren Yurtesen | Assignee: | Eduards Matuls (Inactive) |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | description, macro, template, | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
trigger_ifcontrol actual.png
trigger_ifcontrol.png
|
| Description |
|
Steps to reproduce:
Result: The trigger description (amongst other info): 1=1 - user can redefine Context macro to value - 0. That marks this interface as not important. No new trigger will be fired if this interface is down. Expected:
{$IFCONTROL:"{#IFNAME}"}=1 - user can redefine Context macro to value - 0. That marks this interface as not important. No new trigger will be fired if this interface is down.
It is somewhat a cosmetic error but I was confused to see 1=1 in the error when I saw this message first time. Is it not possible to escape variables in description so Zabbix won't evaluate them? |
| Comments |
| Comment by Eduards Matuls (Inactive) [ 2020 Jun 26 ] |
|
Hello! Thank you for reporting the issue! Can you please attach a screenshot of trigger configuration? Regards, |
| Comment by Evren Yurtesen [ 2020 Jun 28 ] |
|
@Eduards Matuls sure, it is the default trigger prototype which ships with zabbix. I am attaching both the trigger prototype screenshot and also what it prints when there is a problem...
|
