[ZBXNEXT-1636] Show action name for message actions in event details view Created: 2013 Feb 25  Updated: 2018 Apr 26

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

Type: Change Request Priority: Minor
Reporter: Marc Assignee: Unassigned
Resolution: Unresolved Votes: 6
Labels: actions, details, event, name, patch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux, CentOS-6.3, PostgreSQL 9.1.8, Apache HTTPD-2.2.15, PHP-5.3.3


Attachments: File zabbix-2.0.8-zbxnext-1636.patch    
Issue Links:
Duplicate
is duplicated by ZBX-10606 Frontend Monitoring->Events section "... Closed

 Description   

Currently there seems to be no way to identify which action was responsible for a message.
Beside the informational benefit it would make it a lot easier to fix sending of multiple messages for the same trigger caused by sub-optimal configured action conditions.

 Comments   
Comment by richlv [ 2013 Feb 25 ]

similar to ZBXNEXT-1533 (showing action in auditlog)

Comment by Volker Fröhlich [ 2013 Oct 08 ]

Unfortunately, just as in ZBXNEXT-421, the permission model does not intend unprivileged users to see action or alert details. Since being an admin is not enough to see every action that could run on a specific host's event, the options are:

  • Receive information for some actions but not for others
  • Change the permission model
  • Limit it to super-admins

The attached patch takes the latter approach. It is a cumulative patch of ZBXNEXT-421, ZBXNEXT-1533 and this issue with minor improvements.

Comment by Pavels Jelisejevs (Inactive) [ 2014 Feb 14 ]

Limiting this feature to super admins only greatly reduces it's potential, since this information will be mostly interesting to people, who configure actions, that is, admins.

Comment by Dimitri Bellini [ 2016 Aug 31 ]

Please provide a solution to this kind of request, in most case is very useful.
Thanks

Generated at Tue Apr 23 20:08:40 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.