[ZBXNEXT-3432] Please consider {HOST.HOST} and {HOST.IP} to be supported in Event tags Created: 2016 Sep 10  Updated: 2024 Apr 10  Resolved: 2017 Apr 27

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: 3.2.0
Fix Version/s: 3.4.0alpha1

Type: Change Request Priority: Trivial
Reporter: Vitaly Zhuravlev Assignee: Unassigned
Resolution: Fixed Votes: 2
Labels: eventcorrelation, macros, tags
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File ZBXNEXT-3432.patch     PNG File screenshot-1.png     PNG File screenshot-2.png     PNG File screenshot-3.png     PNG File screenshot-4.png     PNG File screenshot-5.png    
Issue Links:
Causes
causes ZBX-14851 Incorrect display of the host visible... Closed
Team: Team A
Sprint: Sprint 3, Sprint 4, Sprint 5, Sprint 6
Story Points: 3

 Description   

Please consider {HOST.HOST} and {HOST.IP} to be supported in Event tags.

Event with value of {HOST.HOST} is required in many scenarios of Global Correlation.

Or even better: Consider implementing built-in event tags, first of which would be Hostname.

 Comments   
Comment by Patrick Fouquet [ 2016 Sep 10 ]

+1 for {INVENTORY.*} macros

Comment by Alexander Vladishev [ 2016 Oct 05 ]

Related issue: ZBXNEXT-3480

Comment by Vladislavs Sokurenko [ 2017 Mar 15 ]

Could you please try attached patch and see if it works for you ? vzhuravlev

Comment by Vitaly Zhuravlev [ 2017 Mar 15 ]

vso, thanks I'll try that right now

Comment by Vitaly Zhuravlev [ 2017 Mar 15 ]

vso, patch worked! Applied to 3.2.4. Thanks for quick response.

Here is an example with many alarms now correlated using Global correlation:

Comment by Vitaly Zhuravlev [ 2017 Mar 28 ]

This request is basically about giving users as much flexibility as possible with correlation. In order to do that that they need to have ability to populate tags with information that they might be needed.

{HOST.*}

and

{INVENTORY.*}

are example information sources. As an alternative, those attributes (inventory fields, host names etc) could be allowed to be accessed from Global Correlation directly then you wouldn't require to populate tags with it.

Comment by Glebs Ivanovskis (Inactive) [ 2017 Mar 28 ]

Guys who voted, can you please describe a use case where you need {HOST.*} macros in tags? Is support of {HOST.*} macros in tags exactly what you want or could Host name condition type in global correlation configuration be more suitable?

Comment by Vitaly Zhuravlev [ 2017 Mar 28 ]

{INVENTORY.LOCATION} can be used to correlate site related alarms: Power issues, Temperature issues, Connectivity issues

Comment by Glebs Ivanovskis (Inactive) [ 2017 Mar 28 ]

Ok, makes sense. I see it as taking Host inventory filter from Monitoring->Problems and putting it into Configuration->Event correlation.

Comment by Vladislavs Sokurenko [ 2017 Apr 12 ]

Fixed in development branch:
svn://svn.zabbix.com/branches/dev/ZBXNEXT-3432

Comment by Andris Zeila [ 2017 Apr 18 ]

Successfully tested.

Note that heavy usage of host macros in trigger tags can lead to performance problems because of configuration cache locking. After ZBXNEXT-3659 is finished we could in theory resolve also host macros during configuration sync. However this would require additional development as only user macro resolving support will be added in ZBXNEXT-3659.

Comment by Vladislavs Sokurenko [ 2017 Apr 18 ]

Released in:

  • 3.4.0alpha1 r67375
added support of {HOST.ID}, {HOST.HOST}, {HOST.NAME} macros in tags, improved to read those from cache; added support of interface macros in tags
Comment by Martins Valkovskis [ 2017 Apr 21 ]

Updated documentation:

vso CLOSED

Generated at Fri Apr 26 01:26:10 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.