[ZBXNEXT-990] Allow macro {TRIGGER.EVENTS.UNACK} in trigger expressions Created: 2011 Oct 06 Updated: 2012 Nov 01 Resolved: 2012 Nov 01 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F), Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Major |
| Reporter: | HJ Zimmer | Assignee: | Alexei Vladishev |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | expressions, flexibility, macros, triggers | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
According to docu and confirmed by own tests, this macro cannot be used in trigger expressions. It would be very useful if this were possible because then one could reset the triggers after events have been acknowledged |
| Comments |
| Comment by Alexei Vladishev [ 2012 Oct 15 ] |
|
That feature sounds interesting and is a nice addition to already existing {TRIGGER.VALUE}used for hysteresis. |
| Comment by richlv [ 2012 Oct 31 ] |
|
|
| Comment by Oleksii Zagorskyi [ 2012 Nov 01 ] |
|
Once I observed that such macros can be hard task for DB (in most cases, IMO) - see I would afraid cases when these macros could be used in trigger expression i.e. will be recalculated very often. |
| Comment by richlv [ 2012 Nov 01 ] |
|
reopen to change "Fix Version" |
