screenshot-1.jpg
[ZBX-5417] Trigger overview does not work properly Created: 2012 Aug 06 Updated: 2017 May 30 Resolved: 2012 Aug 09 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Frontend (F) |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | 2.0.3rc1, 2.1.0 |
| Type: | Incident report | Priority: | Critical |
| Reporter: | Alexander Vladishev | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | macros, overview | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
screenshot-1.jpg
|
| Description |
|
After updating Zabbix from 2.0.1 to 2.0.2 the trigger descriptions displays with open macros in the Trigger overview screen and screen element. |
| Comments |
| Comment by Pavels Jelisejevs (Inactive) [ 2012 Aug 06 ] |
|
RESOLVED in svn://svn.zabbix.com/branches/dev/ZBX-5417. |
| Comment by Toms (Inactive) [ 2012 Aug 09 ] |
|
(1) Everything fine, but there is small improvement to be done within this zbx (approved by Sasha). <pavels> RESOLVED. <Toms> CLOSED |
| Comment by Toms (Inactive) [ 2012 Aug 09 ] |
|
(2) It would be nice to comment function you edited - get_triggers_overview() <pavels> RESOLVED. I've also done some refactoring in r29484. <Toms> CLOSED |
| Comment by Toms (Inactive) [ 2012 Aug 09 ] |
|
Review my changes in r29499 |
| Comment by Toms (Inactive) [ 2012 Aug 09 ] |
|
TESTED |
| Comment by Pavels Jelisejevs (Inactive) [ 2012 Aug 09 ] |
|
Fixed in 2.0.3rc1 r29515 and 2.1.0 r29516. CLOSED. |
| Comment by Marc [ 2012 Oct 24 ] |
|
Could it be that this breaks macro substitution in trigger names? |
| Comment by Pavels Jelisejevs (Inactive) [ 2012 Oct 25 ] |
|
Marc, It could. What exactly do you mean? |
| Comment by Marc [ 2012 Oct 25 ] |
|
After upgrading to 2.0.3 macros in trigger names will not get replaced by their values within for example 'Monitoring :: Dashboard' and 'Monitoring :: Triggers'. |
| Comment by Pavels Jelisejevs (Inactive) [ 2012 Oct 26 ] |
|
Could you give a specific example of a trigger that is not resolved correctly? 2.0.3 does indeed have problems with macros; some of them have already been fixed in 2.0.4rc1 under |
| Comment by Marc [ 2012 Oct 26 ] |
|
Sure! Trigger name: 'Expect more than {ITEM.VALUE1} foo processes'Trigger expression: '{Template example:proc.num[foo,root].last(0)}<1' Looks in Dashboard, etc: 'Expect more than {ITEM.VALUE1} foo processes' |
| Comment by Marc [ 2012 Oct 26 ] |
|
Just taken a look into the mentioned issues and I think my problem is already known and fixed by: |
| Comment by Pavels Jelisejevs (Inactive) [ 2012 Oct 26 ] |
|
Good to hear. If you encounter any more problems be sure to let us know. |