[ZBXNEXT-1554] ability to discover arbitrary number of SNMP lld values Created: 2013 Jan 01  Updated: 2015 Aug 05  Resolved: 2015 Jan 22

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Proxy (P), Server (S)
Affects Version/s: 2.0.3
Fix Version/s: 2.5.0

Type: New Feature Request Priority: Major
Reporter: Md.Shafiqul Islam Assignee: Unassigned
Resolution: Fixed Votes: 7
Labels: lld, snmp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

centos 5 zabbix 2.0.0


Issue Links:
Duplicate
is duplicated by ZBXNEXT-2715 Extended SNMP LLD Closed
is duplicated by ZBXNEXT-2214 Complex discovery rules Closed
is duplicated by ZBX-9759 Zabbix 2.5.0 - low level SNMP discove... Closed

 Description   

Dear, I need help with LLD. Thanks to ZABBIX team for coming up with LLD feature almost like Cacti... I had to make separate templates for each of my devices earlier which seems would be much smoother from now on.

Anyways, please help me with LLD. With LLD discovery, if I use ifDescr as discovery key then variable (#SNMPVALUE) stores the description of the interfaces i.e. ge-0/2/0 or something similar as value. I also need to have the ifAlias value shown.

Note: I tried several way around...

1) Using ifAlias as discovery parameter. But this only shows interfaces with Alias being given there. Interfaces without Alias are not shown.

2) Creating two discovery rules. One with ifDescr & one with ifAlias. But I don't know if the two separate variables (#SNMPVALUE)'s are created or even those variables can be interlinked or not.

In short, I require a way around to get the LLD create my items/triggers/etc with both ifDescr (ge-0/2/0) && - ifAlias (Connected to XYZ) in there like cacti...

Note: I see 2.0.0 LLD SNMP built-in template already has sever items created under it.One of those is Alias. Can I use this Alias varibale in trigger/graph/other prototypes?

For example: where ifDescr is used as discovery parameter, is it possible to create a trigger name like: "Interface down on {HOST.NAME} interface {#SNMPVALUE} ifAlias{#SNMPINDEX} or IF-MIB::ifAlias{#SNMPINDEX} etc etc...

please help.

Thanks,
Shafiq

Specification: https://www.zabbix.org/wiki/Docs/specs/ZBXNEXT-1554



 Comments   
Comment by richlv [ 2013 Jan 02 ]

this was initially requested in ZBXNEXT-581 , but it was decided to leave that issue specifically for multiple lld macro filtering.

in this case it would be best if we could specify base OID and lld macro that this subtree should populate

Comment by Filipe Paternot [ 2013 Dec 10 ]

This is specially useful when monitoring loadbalancers, because they usually have their OIDs formed as follow:

desired_oid.virtual_ID.object_id

So, we need to parse two trees to build the full OID that we need to get the value we need. This is not as trivial as interfaces or disks IDs.
mib.vitual_ids
mib.object_ids

PS: today i do that using the agent to do just that and return in a JSON format to build the values.. This is much more a Macgyver than a solution.

Comment by Oleg Ivanivskyi [ 2014 Jun 27 ]

Looks like a duplicate of ZBX-3449...
What do you think?

<richlv> no, that one is different. it's about discovering, for example, MIB::OID.INDEX.GOES.HERE
this one is about discovering

  • MIB::OID1.INDEX
  • MIB::OID2.INDEX
    ...
  • MIB::OIDn.INDEX
Comment by Marc [ 2014 Nov 07 ]

How about enclosing the OID/Macro list in quotation marks?

Comment by Andris Zeila [ 2015 Jan 12 ]

(1) Documentation

Note that screenshots haven't been changed yet, and maybe we should improve the SNMP OID example to use the additional macros returned by discovery.

sasha CLOSED

Comment by Andris Zeila [ 2015 Jan 12 ]

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

Comment by Alexander Vladishev [ 2015 Jan 12 ]

(2) quote_key_param() should be used in upgrade patch to avoid creating illegal keys

wiper RESOLVED in r51572

sasha Great! Take a look at my changes in r51580.

wiper CLOSED

Comment by Alexander Vladishev [ 2015 Jan 13 ]

(3) The new discovery check fails if processed as generic item

OID "discovery[{#SNMPVALUE}, ifDescr]" contains unsupported parameters.

wiper RESOLVED in r51569

sasha CLOSED

Comment by Alexander Vladishev [ 2015 Jan 13 ]

(4) AGENT_REQUEST should be initialized before call of parse_item_key()

wiper RESOLVED in r51566

sasha CLOSED

Comment by Alexander Vladishev [ 2015 Jan 13 ]

(5) Discovered result should be natively sorted

Before:

{"{#SNMPINDEX}": "1", "{#SNMPVALUE}": "1"},
{"{#SNMPINDEX}": "2", "{#SNMPVALUE}": "2"},
{"{#SNMPINDEX}": "3", "{#SNMPVALUE}": "3"},
{"{#SNMPINDEX}": "4", "{#SNMPVALUE}": "4"},
...

After:

{"{#SNMPINDEX}": "24", "{#SNMPVALUE}": "24"},
{"{#SNMPINDEX}": "18", "{#SNMPVALUE}": "18"},
{"{#SNMPINDEX}": "15", "{#SNMPVALUE}": "15"},
{"{#SNMPINDEX}": "4158", "{#SNMPVALUE}": "HP ProCurve Switch software loopback interface"},
...

wiper RESOLVED in r51571

sasha Thanks! Take a look at my changes in r51581.

wiper CLOSED

Comment by Alexander Vladishev [ 2015 Jan 13 ]

(6) Memory leak: missing call of zbx_json_free()

wiper RESOLVED in r51566

sasha CLOSED

Comment by Alexander Vladishev [ 2015 Jan 13 ]

(7) Take a look at my changes in r51564.

wiper Thanks, CLOSED

Comment by Andris Zeila [ 2015 Jan 14 ]

Released in:

  • pre-2.5.0 r51589
Comment by Alexander Vladishev [ 2015 Jan 16 ]

(8) Upgrade patch should check the resulting OID

wiper RESOLVED in r51661

sasha CLOSED

Comment by Andris Zeila [ 2015 Jan 22 ]

Released in:

  • pre-2.5.0 r51762
Generated at Fri Mar 29 03:34:46 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.