[ZBX-5276] {HOST.CONN} is translated in send alerts but nowhere in frontend Created: 2012 Jul 05 Updated: 2017 May 30 Resolved: 2012 Jul 05 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Incident report | Priority: | Minor |
Reporter: | Alexandru Nica | Assignee: | Unassigned |
Resolution: | Duplicate | Votes: | 0 |
Labels: | macros | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
SInce zabbix 2.0.0 a few new macros have been supported in trigger names. These are correctly translated when sending alerts but are not translated anywhere in the frontend, like other marcos are. This led me to the initial conclusion that the feature does not work. For example {HOSTNAME}is translated with the actual hostname when viewing host items or dashboard. {HOST.CONN}, {IPADDRESS}and probably others are not. |
Comments |
Comment by richlv [ 2012 Jul 05 ] |
what interfaces does your host have ? |
Comment by Alexandru Nica [ 2012 Jul 05 ] |
A single IP address |
Comment by richlv [ 2012 Jul 05 ] |
...but what interface type is it ? |
Comment by Alexandru Nica [ 2012 Jul 05 ] |
Agent interface... sorry |
Comment by richlv [ 2012 Jul 05 ] |
{HOST.CONN}
and {HOST.IP} are properly resolved for me in the dashboard when used in trigger names. can you please give exact steps to reproduce the problem ? |
Comment by Alexandru Nica [ 2012 Jul 05 ] |
I have a template with one item with key="icmpping[ {HOST.CONN}, 4, 25, 32, 500]" and a single trigger with name="RT Router interface {HOST.CONN}status down" and expression="{RT Router:icmpping[ {HOST.CONN}, 4, 25, 32, 500].avg(180)}=0". Just updated to 2.0.1 and issue is still present. |
Comment by richlv [ 2012 Jul 05 ] |
in configuration these macros are not expanded to show you what is the actual string, so that's ok. ok, found where they were not expanded in dashboard - "system status" widget. luckily, that's already fixed in |