Ad Widget

Collapse

Zabbix "overloading" of item keys

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jhgrc
    Member
    • Jun 2009
    • 52

    #1

    Zabbix "overloading" of item keys

    Network capacities are going over 4Gbps limit which is the maximum speed of ifSpeed OID (Gauge32). Beyond 2**32-2 you need to use ifHighSpeed OID times 10^6.

    No theoretical problem there to query different variables.

    My problem is that I want to query it to single key and I'd prefer without external script like if.speed (or my own perl version similar to it).

    I tried making to discoveries with filter of max 32-bit gauge and reverse of it. So in theory only one discovery would match and after discovery only one item prototype gets created, one with ifspeed and another one with ifhighspeed.

    The problem is that Zabbix GUI does not allow me to save 100% item prototype key inside same template. I need to have it on same template so that I can use it to calculations like:

    - percentile speed relative to ifspeed/ifhighspeed
    - triggers of inbound/outbound speed relative to ifspeed/ifhighspeed
    - etc

    Have you found any way to go around this limitation? I want to have ifspeed in single item key for multiple trigger expressions and calculated items. Otherwise I need to clone whole template SNMP Interfaces which sounds quite "stupid".
    Last edited by jhgrc; 10-01-2017, 13:39. Reason: typo fixing
  • jhgrc
    Member
    • Jun 2009
    • 52

    #2
    My current solution is to have template for snmp interfaces with 3 LLD autodiscoveries.

    1 - collect all not affected OIDs
    2 - ifSpeed oid + calculated utilization (from OID from LLD1 and ifSpeed) + trigger with LLD-filter if ifSpeed < 2**32-1
    3 - ifHighSpeed oid + calc. util + trigger if LLD-filter ifSpeed = 2**32-1

    But I really would like to have something more robust.

    Another example..

    ifHCInOctets and ifInOctets. Use HC always when available but automatically use non-HC if not available. Because this would again make LLD more complicated with above ifSpeed/ifHighSpeed discovery. And for load I do not want to double-poll for sure.

    Comment

    Working...