Capture - 2023-01-05.PNG
[ZBX-22176] Undefined Macro isn't marked as Undefined when it should be Created: 2023 Jan 05 Updated: 2023 Dec 22 Resolved: 2023 Dec 22 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | None |
| Affects Version/s: | 6.2.6 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | Brad Turnbough | Assignee: | Oleksii Zagorskyi |
| Resolution: | Won't fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 20.04 (fully patched) |
||
| Attachments: |
Capture - 2023-01-05.PNG
|
| Description |
|
Brief Synopsis:
Create a template with any name.
Create an item (within the template) with the following key: net.if.in[\{$SNIFFERNICIP}]
Create a trigger referencing the item (above) with the following information: name: {HOST.NAME} - The Lansweeper Sniffer Interface may be having issues. Please investigate. expression: max(/BIC - Lansweeper Sniffer Network Interface/net.if.in[\{$SNIFFERNICIP}],30m)<"2000" Do not define the "SNIFFERNICIP" macro on the host or anywhere in the zabbix system.
Expected outcome: After some time, the trigger needs to be marked as 'undefined' and a reason needs to specify "Undefined Macro." The trigger should not be placed into a 'problem' state.
Actual outcome: The trigger is NOT marked as 'undefined', however the trigger still goes into a problem state (reference screenshot) |
| Comments |
| Comment by Oleksii Zagorskyi [ 2023 Dec 22 ] |
|
This cannot be considered as a bug. If you do not like current behavior - feel free to register a ZBXNEXT. But first check for a possibly existing one already. |