[ZBX-1654] disabled trigger shown in a map as not disabled Created: 2010 Jan 06 Updated: 2017 May 30 Resolved: 2010 Jan 21 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Frontend (F) |
| Affects Version/s: | 1.8, 1.9.0 (alpha) |
| Fix Version/s: | 1.8.1 |
| Type: | Incident report | Priority: | Blocker |
| Reporter: | richlv | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
element_details.png
parent_map.png
submap.png
trigger_details.png
|
| Description |
|
adding a map element 'map' shows incorrect (not matching) trigger counts. 1. only one problem can be seen in the submap, and monitoring -> triggers also shows only single active trigger for all/all hosts. parent map shows 2 problem triggers. 2. only one unknown trigger can be seen in the submap, but parent map shows 6 unknown triggers |
| Comments |
| Comment by richlv [ 2010 Jan 06 ] |
|
situation is slightly better in dev branch zbx-1647-map 1. problem trigger seems to be caused by a disabled trigger being added directly to the map, not as a part of a host - such a disabled trigger shows up as a problem. 2. unknown trigger count is 3, which is correct attaching screenshots from this branch |
| Comment by Artem Suharev (Inactive) [ 2010 Jan 21 ] |
|
Trivial fix. Fixed directly 1.8 branch. Rev. 9496 |
| Comment by richlv [ 2010 Jan 21 ] |
|
confirming the fix in trunk rev 9500. |