LLD rules and various priority on interfaces - idea needed

[jacek]

Hi,

I'd like to ask for some kind of brain strom, from which propably some solution would pop up.

I've hundreds of switches in monitored network with various services on their interfaces. Some of them are more important, some of them are there just for a testing purposes. On top of that, I'd like to have a mechanism automatically creating triggers for these more important interfaces.

Right now, I have a multiple LLDs (with different filters) on a single host. Each LLD operates on the same data and creates slightly different output (for example items with smaller interval, additional triggers etc.).

Unfortunately, this solution is pretty weak:
- I'm polling for the same data several times just for filtering purposes,
- similar items (like incoming traffic ) has a different keys (for example: InOctets.Important.{#INDEX}, InOctets.Tests.{#INDEX}), and in my case changing alias of interface (by adding appropriate tag in the description of interface) is going to create a new item with new history, duplicate graph etc.

Is there an option to create a template only with triggers? Have any of you similar need and handles it in wiser way?

Many thanks
Jacek.

[hardbone12]

You can try to use a host by running scripts to do the work of the LLD

1.Use a script to get the interface description
2.Using regular expressions grouping these interfaces
3.Modify item name, key or group by zabbix api

This can save your item of historical data and to reduce the create of new item

Sorry, I just think this way can be achieved, but I didn't try it.