[ZBX-5946] Item prototypes generate not usable items name in trends (database) Created: 2012 Dec 05  Updated: 2017 May 30  Resolved: 2012 Dec 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S), Templates (T)
Affects Version/s: 2.0.2
Fix Version/s: None

Type: Incident report Priority: Minor
Reporter: yayo Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Server: CentOS
Target Host: Windows Server (Any Versions)



 Description   

When add template "Windows OS Template" that use Item prototypes (like "Incoming network traffic on

{#IFNAME}

") all works good but items are called "Incoming network traffic on $1" and are not suitable when we extract trends from database.

Items linked to an host via template must have the right name (for example: "Incoming network traffic on HP NC373i Multifunction Gigabit Server Adapter") for using data from zabbix



 Comments   
Comment by yayo [ 2012 Dec 05 ]

Extra informations:

  • Items like "Incoming network traffic on HP NC373i Multifunction Gigabit Server Adapter" are generated from item prototypes "Incoming network traffic on {#IFNAME}

    " used in discovery rules (like: Network interface discovery)

  • Items are displayed correctly in fronted ("Incoming network traffic on HP NC373i Multifunction Gigabit Server Adapter") but are stored in database with wrong name "Incoming network traffic on $1"
Comment by richlv [ 2012 Dec 05 ]

no bug here - $1 positional reference is used in item prototype. it definitely should not be arbitrarily replaced

Comment by yayo [ 2012 Dec 06 ]

ok $1 is positional reference in the item prototypes but, items generated by item prototypes are stored with the positional reference, not with the "real" name. When our business aggregator read this infromation, every (for example) incoming traffic for every nic are read as if it were a single nic with value "Incoming network traffic on $1" and there is no table to merge this value in the right way

Generated at Sun May 11 07:47:36 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.