item groups?

[rd67]

Is there any way to manage items as groups of items in Zabbix?

I'm trying to move from PRTG to Zabbix , but while Zabbix seems to be at the same level or even more powerful than PRTG, Zabbix GUI\UX seems really behind.

In PRTG there are devices (Zabbix hosts) --> sensors (no equivalent in Zabbix?) --> channels (Zabbix items)

e.g.: in PRTG for a device (host) there is one sensor for each network interface and each interface sensor has as many channels (items) as metrics to be collected for that interface (traffic in, traffic out, errors in, etc.)

This way the user is not overwhelmed with having to navigate\search hundreds of items per host.
E.g. to delete or disable all items related to the same network interface all is needed is to select the single interface sensor.

As a plus, having item groups would also allow to set some parameters at the item group level (this is what PRTG does) instead of setting the values on each item.
I know Zabbix has mass edit, but item group settings would be more reliably applied.

Am I missing something and Zabbix already has a way to group items or a similar feature?

[Markku]

Tags can be used for that (among other uses).

Markku

[cyber]

I would say that in a way discovery takes that "sensor" place. It can be configured to find only required interfaces and then create items for them. There are also macros with context, which allow setting different values for triggers for different objects. And there's also discovery overrides, which allow additional manipulation of discovered things.
But as Markku noted, tagging is helpful and simplifies selecting related items/triggers. And these can also be added during discovery.

[rd67]

Thanks both for your replies.

I know that with tags and searches in the end you can select what you need.
But it's much slower and convoluted than having item groups.

Note that in PRTG these item groups are not manually created and are not optional: channels (items) cannot exist outside of sensors (item groups).
E.g. even a custom check for a single OID will be automatically created as one channel (item) inside one sensor (item group)