[ZBXNEXT-1288] {EVENT.ACK.HISTORY} should work in recovery message too, not only in notification Created: 2012 Jun 22 Updated: 2014 Jun 16 Resolved: 2014 Jun 16 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Server (S) |
| Affects Version/s: | 1.8.13, 2.0.0 |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Minor |
| Reporter: | Ricardo Felipe Klein | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 2 |
| Labels: | acknowledges, actions, events, macros, recovery, trivial | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
N/A |
||
| Issue Links: |
|
||||||||
| Description |
|
I think {EVENT.ACK.HISTORY} should be avaiable on Recovery message, so, when something gets back ok I can know if was someone who make something or the issue has just finished by itself.I tried to use this as recovery message, but, {EVENT.ACK.HISTORY} comes empty: Trigger: {TRIGGER.NAME}Trigger status: {TRIGGER.STATUS}Trigger severity: {TRIGGER.SEVERITY}Event Date: {EVENT.DATE}Item values: 1. {ITEM.NAME1}( {HOST.NAME1}: {ITEM.KEY1}): {ITEM.VALUE1}Issue History: |
| Comments |
| Comment by Ricardo Felipe Klein [ 2012 Jun 22 ] |
|
{EVENT.ACK.HISTORY}
<== forgot to close the "}" here, but it is correct on my zabbix configuration... |
| Comment by richlv [ 2013 Apr 15 ] |
|
this request probably is about showing ack history of the original problem event, not of the recovery event (which is less likely to have acknowledgements) somewhat similar change was made to EVENT.ID in |
| Comment by Ricardo Felipe Klein [ 2013 Apr 15 ] |
|
richlv, right, should be usefull see all ack history of the problem when you get the recovery message, so, fast way to know who did what to solve the problem. |
| Comment by Oleksii Zagorskyi [ 2014 Jun 16 ] |
|
According to my comment https://support.zabbix.com/browse/ZBXNEXT-384#comment-96655 it indeed has been implemented. |