I've tried a new alpha version of Zabbix, and one of the most important improvements for me was snmp.autodiscovery.
But as I can see, this feature is not yet ready enough, so I want to make a few suggestions about it.
First, support of dynamic indexes as mentioned here:
And the second is how dynamic indexes work with application. Now you can set application for each item of discovery rule. Let's say, we are adding interface informaton like ifDescr, ifIndex, ifInOctets etc. Following this logic, you can place all ifDescr items into one application and all ifIndexes into another. Maybe I'm missing something, but in my opinion it's completely useless. Instead, I want to place all items for one interface into one application and for another - to another one. Then I can open, let's say, Latest data and see list of interfaces represented by applications. That's what I do now manually by preparing template xml for each interface and then importing it. It's a very boring work when you have lots of interfaces, but it makes a good results for me.
Now, I don't see the way I can group item by interfaces even manually because I can't edit autodiscovered items.
What I want is to have the ability to enter a name for application that discovered item will belong to using macros (at least {#SNMPINDEX} is required, but it would be great to include there ifDescr or ifName or ifAlias). When the script sees that application with that name exists, it has to add item to it, otherwise - create it first.
Thank you!
Best Regards, Vadim.
But as I can see, this feature is not yet ready enough, so I want to make a few suggestions about it.
First, support of dynamic indexes as mentioned here:
And the second is how dynamic indexes work with application. Now you can set application for each item of discovery rule. Let's say, we are adding interface informaton like ifDescr, ifIndex, ifInOctets etc. Following this logic, you can place all ifDescr items into one application and all ifIndexes into another. Maybe I'm missing something, but in my opinion it's completely useless. Instead, I want to place all items for one interface into one application and for another - to another one. Then I can open, let's say, Latest data and see list of interfaces represented by applications. That's what I do now manually by preparing template xml for each interface and then importing it. It's a very boring work when you have lots of interfaces, but it makes a good results for me.
Now, I don't see the way I can group item by interfaces even manually because I can't edit autodiscovered items.
What I want is to have the ability to enter a name for application that discovered item will belong to using macros (at least {#SNMPINDEX} is required, but it would be great to include there ifDescr or ifName or ifAlias). When the script sees that application with that name exists, it has to add item to it, otherwise - create it first.
Thank you!
Best Regards, Vadim.