Dear All,
Our infrastructure uses Zabbix 2.2. My current dilemma is the following one:
I would like to discover and monitor filesystems using low-level discovery but also distribute different discovery rules over several templates which could be linked to a given host.
The rationale behind this is to have a common base template for our hosts that monitors standard local filesystems (i.e. ext3/4, zfs, xfs). Some exceptional hosts would then be linked to a supplementary specific template to also monitor another type of filesystem (i.e. cvfs and fhgfs) using a different regex for the FSTYPE.
The idea of having 2 templates is to keep host configuration more easy to manage, that is, without overriding items/discovery rules of a template at the host level.
The problem we encounter is that the discovery key "vfs.fs.discovery" has to be unique, so when we want to link this supplementary template to a host we get a "key already in use" error. The same is true for the item prototype keys.
I understand the reasons for this, but I would like to know if somebody has an elegant solution for this kind of problem?
Any ideas are welcome
Kind regards,
Volker
Our infrastructure uses Zabbix 2.2. My current dilemma is the following one:
I would like to discover and monitor filesystems using low-level discovery but also distribute different discovery rules over several templates which could be linked to a given host.
The rationale behind this is to have a common base template for our hosts that monitors standard local filesystems (i.e. ext3/4, zfs, xfs). Some exceptional hosts would then be linked to a supplementary specific template to also monitor another type of filesystem (i.e. cvfs and fhgfs) using a different regex for the FSTYPE.
The idea of having 2 templates is to keep host configuration more easy to manage, that is, without overriding items/discovery rules of a template at the host level.
The problem we encounter is that the discovery key "vfs.fs.discovery" has to be unique, so when we want to link this supplementary template to a host we get a "key already in use" error. The same is true for the item prototype keys.
I understand the reasons for this, but I would like to know if somebody has an elegant solution for this kind of problem?
Any ideas are welcome
Kind regards,
Volker