[ZBX-20532] Default "Linux by Zabbix agent" template uses {#IFALIAS} in network discovery Created: 2022 Feb 03  Updated: 2024 Apr 10  Resolved: 2022 Feb 03

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 6.0.0rc1
Fix Version/s: None

Type: Problem report Priority: Minor
Reporter: Brian van Baekel Assignee: Zabbix Development Team
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2022-02-03 at 13.39.04.png     PNG File Screenshot 2022-02-03 at 13.39.34.png     PNG File Screenshot 2022-02-03 at 13.39.46.png    
Issue Links:
Sub-task
part of ZBX-16896 Linux Templates Speed Change Trigger Closed
Team: Team INT
Sprint: Sprint 85 (Feb 2022)
Story Points: 0.25

 Description   

In template "Linux by Zabbix agent", discovery rule "Network interface discovery" (key net.if.discovery) is, in the item prototype a macro {#IFALIAS} used for tag "description".
However, the result of the discovery is:

[{"{#IFNAME}":"lo"},{"{#IFNAME}":"ens192"}]

So, in Configuration -> hosts -> items, there is a strange tag
In Monitoring -> hosts -> graphs is a strange tag
in Monitoring -> latest data is a strange tag.

We can filter on tags, and as there might be quite a few {#IFALIAS} values not resolved, we're breaking the concept there; screenshots attached.

Did not check other templates, might have the same issues.



 Comments   
Comment by Oleksii Zagorskyi [ 2022 Feb 03 ]

I can confirm it. The template got changes for 6.0 (if compare with 5.4) and currently there are 3 tags for item prototype:

component -> network
description -> {#IFALIAS}
interface -> {#IFNAME}

Previously there was only one tag:

Application -> Interface {#IFNAME}
Comment by Aleksandrs Larionovs (Inactive) [ 2022 Feb 03 ]

Will be resolved in ZBX-16896

Comment by dimir [ 2022 Feb 03 ]

If so, should we close this one as duplicate?

Comment by Alexander Vladishev [ 2022 Feb 03 ]

Closed as duplicate.

Comment by XinWang [ 2022 Jun 09 ]

does this really solved? not any tags been added to net.if.discovery in 6.0.4

Generated at Mon Apr 07 23:53:50 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.