[ZBX-10362] Trigger URL seems to require the flag filter_rst=1 Created: 2016 Feb 08 Updated: 2017 May 30 Resolved: 2016 Feb 29 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Frontend (F) |
| Affects Version/s: | 2.4.7, 3.0.0alpha6 |
| Fix Version/s: | 3.0.0rc2 |
| Type: | Incident report | Priority: | Major |
| Reporter: | James Sperry | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | regression | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
In Zabbix 2.2 we set the trigger URL to http://<zabbix fqdn>/events.php?triggerid= {TRIGGER.ID} so that there is a link directly to the event of the trigger. This makes it convenient for our NOC to go directly to the issue and take proper action.I noticed in 2.4 it doesn’t work that way. Now I’m testing zabbix 3.0 and I see it’s also remembering the previous filter, and therefore not going to the proper event. Looking at the code for events.php, I see there is a flag for filter_rst. I set that to 1 in the Trigger URL and now the link provided in the email alerts goes to the proper place. I use this URL: http://<zabbix fqdn>/events.php?filter_rst=1&triggerid={TRIGGER.ID} Can this information be added to the documentation here: |
| Comments |
| Comment by Alexander Vladishev [ 2016 Feb 09 ] |
|
Thank you for reporting your issue. Seems resolving of the {TRIGGER.ID} macro is broken in trigger URL field. |
| Comment by Alexander Vladishev [ 2016 Feb 09 ] |
|
Fixed in the development branch svn://svn.zabbix.com/branches/dev/ZBX-10362 |
| Comment by Oleg Egorov (Inactive) [ 2016 Feb 10 ] |
|
(1) No string changes sasha CLOSED |
| Comment by Oleg Egorov (Inactive) [ 2016 Feb 10 ] |
|
TESTED |
| Comment by Alexander Vladishev [ 2016 Feb 10 ] |
|
Fixed in pre-3.0.0rc2 r58379. |
| Comment by Alexander Vladishev [ 2016 Feb 10 ] |
|
ejames, trigger URL in 3.0 must be events.php?triggerid={TRIGGER.ID}&filter_set=1 filter_rst flag resets all filter parameters. |
| Comment by richlv [ 2016 Feb 10 ] |
|
this issue went through the documentation phase and was set as documented, even though the comment above by sasha did not land in the documentation. should this issue be reopened ? |
| Comment by Martins Valkovskis [ 2016 Feb 11 ] |
|
Documented in:
sasha CLOSED |
| Comment by richlv [ 2016 Feb 11 ] |
|
thank you, martins-v - but maybe it could be moved together with other page parameters in https://www.zabbix.com/documentation/3.0/manual/web_interface/page_parameters ? martins-v Thanks for the suggestions, https://www.zabbix.com/documentation/3.0/manual/web_interface/page_parameters and the event page updated accordingly. sasha Great! CLOSED |
| Comment by richlv [ 2016 Feb 15 ] |
|
thank you, martins-v. for that page, maybe it's better to reformat to follow the same style ? btw, this sentence seemed weird : "Access to events of a specific trigger, which may be useful for notifications is to use a URL like:" - seems to be copy-paste mangled a bit ? |
| Comment by James Sperry [ 2016 Feb 26 ] |
|
Just to follow up, I upgraded to 3.0.0rc2 and had to add the hostid parameter to get it to go to the proper triggerid. Without the hostid the link would not show the proper trigger. Perhaps someone could test this and update the documentation to note this. http://<zabbix fqdn>/events.php?triggerid={TRIGGER.ID}&filter_set=1&hostid={HOST.ID} Thanks for getting this fixed. sasha Thank you for a comment. We are created a new bug report: |