[ZBX-2385] {TRIGGER.EVENTS.UNACK}, {TRIGGER.EVENTS.PROBLEM.UNACK} functionality Created: 2010 Apr 27 Updated: 2017 May 30 Resolved: 2010 Jun 03 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | None |
Affects Version/s: | 1.8.2 |
Fix Version/s: | 1.8.3 |
Type: | Incident report | Priority: | Minor |
Reporter: | Alexey Fukalov | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
{TRIGGER.EVENTS.UNACK}
- it will return number of ALL unacknowledged events for a trigger {TRIGGER.EVENTS.PROBLEM.UNACK}- it will return number of unacknowledged PROBLEM events for a trigger |
Comments |
Comment by Alexey Fukalov [ 2010 Apr 27 ] |
|
Comment by Alexey Fukalov [ 2010 Apr 28 ] |
{TRIGGERS.UNACK}
- all unacknowledged triggers count {TRIGGERS.PROBLEM.UNACK}- problem unacknowledged triggers count |
Comment by Artem Suharev (Inactive) [ 2010 May 05 ] |
In current frontend we can't ack events in OK state, why they counted? or why not counted unknown events? Other aspects works fine (but slow due to number of unack events, in my test system it's ~ 100k). |
Comment by Alexey Fukalov [ 2010 May 06 ] |
branches/1.8 11831 |
Comment by richlv [ 2010 May 28 ] |
as pointed out by zalex_ua, documentation has not been updated |
Comment by Oleksii Zagorskyi [ 2010 May 31 ] |
richlv, Alexei, I think this Improvement should be FULLY reflected at this point |
Comment by richlv [ 2010 May 31 ] |
this doesn't seem to work as expected (trunk rev 12370). in maps, {TRIGGER.EVENTS.UNACK}seems to expand in total amount of unacknowledged events, and {TRIGGER.EVENTS.PROBLEM.UNACK}- to unacknowledged events for the current element, disregarding current trigger state. instead, first should be limited by map element (trigger, host, hostgroup, map), and second should be both limited by map element, as well as only counting unacknowledged events for triggers that are currently in the problem state. please see http://www.zabbix.com/documentation/1.8/manual/config/macros#list_of_supported_macros for descriptions - would be nice to doblecheck that both frontend (in map labels) and server (in notifications) follow those definitions, as currently in the manual. |
Comment by richlv [ 2010 Jun 02 ] |
changes again. instead, existing macros stay the way they are and a new one is introduced : {TRIGGER.PROBLEM.EVENTS.PROBLEM.UNACK}- shows amount of unacknowledged events for triggers that are currently in the problem state |
Comment by Alexey Fukalov [ 2010 Jun 03 ] |
|
Comment by richlv [ 2010 Jun 03 ] |
confirming the implementation in dev branch rev 12517. |
Comment by Alexey Fukalov [ 2010 Jun 03 ] |
branches/1.8 12527 |