Low-Level Discovery, problem of selectivity

[xpasha]

Hello, all

I tried to use low-level discovery feature in Zabbix 2.0.4, all is good but the problem is that Zabbix pull all the crap from hardware without possibility select for example interfaces, that I really need for monitoring. Is there any way to do that??

Zabbix also has two addons for the solving the same goal - autodiscovery mibs from given host. There is one for 1.8 and one for 2.0. These addons if to believe their descriptions have to get the three of mibs and admin of zabbix can select only that he wants for making Items frim these selected mibs. But in reality both takes mibs three from given hosts but it's impossible to select that you want and make Items from that. Is there any way to do that with plugins or with low-level discovery? It's really annoing adding interfaces from hosts to Zabbix, and impossible to keep all info from all discovered interfaces, becaus in the network with quantity of hosts will produce giant amount of data on the Zabbiz Server. That is the reason why some admins perefers more primitive systems like Cacti, that allows discovery with selections only what you want to watch for.

[Bernd Hohmann]

I tried to use low-level discovery feature in Zabbix 2.0.4, all is good but the problem is that Zabbix pull all the crap from hardware without possibility select for example interfaces, that I really need for monitoring. Is there any way to do that??

Instead of using the default "@File systems for discovery" you can roll your own (or change the global regex for that). Or simply let the auto discovery alone and disable unwanted monitoring in each host.

Bernd

[xpasha]

Instead of using the default "@File systems for discovery" you can roll your own (or change the global regex for that). Or simply let the auto discovery alone and disable unwanted monitoring in each host.

Bernd

Thank you for the reply. The main problem that there is no similarity in the set of choosen interfaces on each device in my network that I would like to monitor. So these interfaces could not be described by any regexp. I just need to get list of MIBs, choose interfaces I need and delete all that I dont need to monitor. And also I did not understand what you meant talking "disable unwanted monitoring". What you meant saying unwanted monitoring. Or you meant I can disable monitoring of not needed interfaces but Items will stay in the Zabbix? If I understood you right, then how can I do that?

Best regards, Paul

[Bernd Hohmann]

Thank you for the reply. The main problem that there is no similarity in the set of choosen interfaces on each device in my network that I would like to monitor. So these interfaces could not be described by any regexp. I just need to get list of MIBs, choose interfaces I need and delete all that I dont need to monitor. And also I did not understand what you meant talking "disable unwanted monitoring". What you meant saying unwanted monitoring. Or you meant I can disable monitoring of not needed interfaces but Items will stay in the Zabbix? If I understood you right, then how can I do that?

As far as I can remember there is a Switch "enable/disable monitoring" for each discovered item.

But now I understand your problem: you're using SNMP discovery, right? Yes - the discovery will grab anything before you can say "Blueberry pie".

I don't think that zabbix can iterate over a file with OIDs, neither it can discover first, displays a list of discovered items where the user can select which stuff to cover.

Bernd

[xpasha]

As far as I can remember there is a Switch "enable/disable monitoring" for each discovered item.

But now I understand your problem: you're using SNMP discovery, right? Yes - the discovery will grab anything before you can say "Blueberry pie".

I don't think that zabbix can iterate over a file with OIDs, neither it can discover first, displays a list of discovered items where the user can select which stuff to cover.

Bernd

Unfortunately, so called low-level discovering don't ask Zabbix admin what to select, it just pull all the crap from device and automatically makes Items and Graphs for every MIB, and there is no possibility to remove anything because these Items and Graphs where created by Template with low-level discovery function activated. You create a host firstly, link it with such Template that for example pulls only MIBs of interfaces(it can be regulated what kind of MIBs to pull and also you can use filter with regexp as I read in docs). But this range of customization of autodiscovery if too wide. Why do I need for example about 50 interfaces when LLD pull it all from core Cisco router? I need only interfaces that are connected to border routers and backbone network.

[Bernd Hohmann]

I know that problem. Usually I'm only interested monitoring the amount of data a router had sent/received from the uplink.

You may try to create a template and use usermacros to identify the OID or Port to monitor, but the best way would be creating the items by hand.

Bernd

[xpasha]

I know that problem. Usually I'm only interested monitoring the amount of data a router had sent/received from the uplink.

You may try to create a template and use usermacros to identify the OID or Port to monitor, but the best way would be creating the items by hand.

Bernd

By hand is more precisely but in our network we have hundred of hosts. Handwork is not solve the problem. I see that no way as to minimize quantity of pulled information, use the only needed interfaces and disable all the is not needed as you advised, or to will try to find way to create Items being disabled, then it would be necessary to enable only selected interfaces.

[Bernd Hohmann]

By hand is more precisely but in our network we have hundred of hosts. Handwork is not solve the problem. I see that no way as to minimize quantity of pulled information, use the only needed interfaces and disable all the is not needed as you advised, or to will try to find way to create Items being disabled, then it would be necessary to enable only selected interfaces.

But I don't think you have hundred of different SNMP devices to monitor. As mentioned before, you may try to create a template and define the port(s) to monitor by a user macro.

Bernd