Help understanding discovery prototype inheritance

[lewiz]

Hello,

I have filesystem discovery enabled for a set of hosts. My configuration is very similar to https://www.zabbix.com/documentation...evel_discovery

My configuration is essentially:

Template Linux OS Filesystem Discovery: as per the docs
Template Linux OS: linked to Template Linux OS Filesystem Discovery
Template Linux Storage Servers: linked to Template Linux OS

When I assign the Template Linux Storage Servers to hosts the relevant items, triggers, etc. from my Template Linux OS Filesystem Discovery are made available.

My question is:

How is inheritance handled? My tests have so far left me unsure. In some instances disabling a specific Template Linux OS Filesystem Discovery trigger prototype at the Template Linux Storage Servers level has disabled the generated triggers on hosts, while others remain active.

I am expecting that any change made to a prototype will be propagated down the stack unless a specific change has been made further down, in which case that overrides.

Can anybody point me to the relevant documentation that explains this in detail, and or provide an authoritative answer.

FYI I came across https://www.zabbix.com/forum/showthread.php?t=40981 which seems relevant but does not exactly match the behaviour that I am seeing.

[BDiE8VNy]

I don't "know" how it works. Till now I thought all changes to prototypes are considered on (re-)discovery.
Do you have waited at least configured 'Update interval' of corresponding LLD rule?

[lewiz]

I think you may well be correct. It seems that eventually things get updated - although prior to re-linking all of my hosts from a particular template the behaviour I was seeing was more erratic. I suspect that somewhere along the way the DB got messed up as I've been making changes all over the place while setting this server up.

As far as I can tell disabling a trigger doesn't make the existing trigger notifications go away though.