[ZBXNEXT-805] Acknowledge overview Created: 2011 Jun 06  Updated: 2023 Jul 24

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: 1.8.4
Fix Version/s: None

Type: New Feature Request Priority: Minor
Reporter: Frank Assignee: Unassigned
Resolution: Unresolved Votes: 11
Labels: acknowledges, dashboard, widget
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian 6 / Apache 2.2.x / PHP 5.3.x / Latest Zabbix Stable


 Description   

It would be nice if there was an "acknowledge overview" page, preferably paginaged and filterable, which shows all the recent acknowledgements.
Since we have multiple persons working with Zabbix at the same moment, it would be an easy tool to see what issues have been (or are being) addressed by whom and when it was acknowledged.

 Comments   
Comment by Andy Goldschmidt [ 2011 Nov 09 ]

this sounds good.

Comment by Nick Duke [ 2013 May 10 ]

I agree, some way to show the acks and the notes left would be nice. Right now in Monitoring > Triggers you can see which have been ack'ed but not what someone typed in when they ack'ed it. Could their ack note be copied in to the comments section as well? To me it seems that ack notes are just lost right now.

Comment by richlv [ 2013 May 10 ]

you can see them if events are expanded, also see ZBX-2622

Comment by Marc [ 2013 May 10 ]

That's right but by a dedicated overview acknowledges might be ordered by date of acknowledge to see what's going on and maybe filtered by user / host resp. user group / host group, etc.

Comment by richlv [ 2017 Nov 07 ]

potentially useful filters :

  • my acknowledgement messages [convenience filter]
  • by user
  • by time period
  • by host group, host
  • first acknowledgement, followup message (both as a filter and visually distinguishing if both displayed)
  • by acknowledgement text (also negated)
  • by trigger severity

it might be also useful to filter ack messages by the target host maintenance status (keeping in mind multihost triggers), but storing that status could be a challenge

Generated at Fri Apr 04 09:47:09 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.