[ZBX-7630] selected host in filter prevents viewing trigger events when coming from dashboard Created: 2014 Jan 09 Updated: 2017 May 30 Resolved: 2014 Apr 07 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | 2.2.2rc1 |
Fix Version/s: | 2.2.4rc1, 2.3.0 |
Type: | Incident report | Priority: | Major |
Reporter: | Aleksandrs Saveljevs | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | events | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
Suppose we go to "Monitoring" -> "Events" and view events for host A. We then go to "Monitoring" -> "Dashboard" and, in "Last 20 issues" widget, click on the link in "Last change" column for a trigger that pertains to host B. On the opened page the trigger filter is correctly set to the trigger we want to see. However, because we have previously selected host A for viewing, no events are shown. |
Comments |
Comment by Pavels Jelisejevs (Inactive) [ 2014 Jan 10 ] |
A related issue - ZBX-7228. |
Comment by Pavels Jelisejevs (Inactive) [ 2014 Jan 10 ] |
Another problem with the trigger filter is that after selecting a host, you can select a trigger from a different host and you won't see any results as well. oleg.egorov Please, fix this issue |
Comment by Eduards Samersovs (Inactive) [ 2014 Feb 03 ] |
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7630 |
Comment by Oleg Egorov (Inactive) [ 2014 Feb 06 ] |
(1) events.php:351 (($_REQUEST['hostid'] > 0) ? '&only_hostid='.$_REQUEST['hostid'] : ''). I think should be changed to: ($_REQUEST['hostid'] ? '&only_hostid='.$_REQUEST['hostid'] : ''). Eduards RESOLVED r.42321 oleg.egorov CLOSED |
Comment by Oleg Egorov (Inactive) [ 2014 Feb 06 ] |
TESTED |
Comment by Eduards Samersovs (Inactive) [ 2014 Feb 12 ] |
Fixed in versions 2.3.0 (trunk) r.42538, 2.2.3rc1 r.42537 |
Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 01 ] |
(2) This caused a regression: when selecting a trigger and switching to a different host with the same trigger, the trigger in the filter must be replaced with the same trigger on the new host. Eduards Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7630 r.43956 |
Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 02 ] |
(3) When we choose a host that does not have this trigger, the filter must be empty. Eduards RESOLVED r.44034 jelisejev CLOSED. |
Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 03 ] |
(4) Please remove the "filter_set" parameter from event links. It changes the behavior of the filter and we would like to avoid that in 2.2. Eduards RESOLVED r.44034 jelisejev CLOSED. |
Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 04 ] |
(5) Open the Events page and select discovery events. Then go to the triggers page and click on the link to open the events for one of the triggers. The link will take you to the discovery events, instead of the trigger events. Eduards RESOLVED r.44072 jelisejev Please add the "source" parameter to the links leading to events page, instead of deducing it from the "triggerid" parameter. Eduards RESOLVED r.44110 jelisejev I've corrected some of the remaining links and made some formatting corrections in r44182, please review. Eduards CLOSED |
Comment by Marc [ 2014 Apr 07 ] |
|
Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 08 ] |
(6) [trunk] We've added new event page links in the trunk. When merging, please make sure (5) is fixed for them as well. |
Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 08 ] |
Marc, it is related, but it will not be fixed in this issue. |
Comment by Pavels Jelisejevs (Inactive) [ 2014 Apr 08 ] |
TESTED. Please review (5) before merging and close it if it's OK. |
Comment by Eduards Samersovs (Inactive) [ 2014 Apr 08 ] |
Fixed in versions 2.3.0 (trunk) r.44185, 2.2.4rc1 r.44184 |