Problems with macroes based from LLD

[geirra]

Testing the LLD macro functions and I'm stuck with an wierd bug.

Rewrote the default linux OS template to the following, using the examples from https://www.zabbix.com/documentation...evel_discovery


Created a global macro thats says:
{$LOW_SPACE_LIMIT} = 20

Now if i create 1 host level macro everything is fine.
Lets say i create
{$LOW_SPACE_LIMIT:/home} = 99
(just to make it trigger)

And this works fine.
Problem arrises when i add more than one.

Lets add {$LOW_SPACE_LIMIT:/storage} = 90

Now the /storage trigger works, but the /home that was working is now suddenly using the default 20 limit.
It does the same in graph also.



If i remove macro for /storage it works as normal within seconds.

If i add a third macro for / it breaks both /home & /storage



This is using zabbix 3.2

[nobodysu]

When LLD is discovered all data is added to the host as regular items and stays there till the expiration date (30 days by default)! It does not matter whether you have changed LLD or unlinked the template.
To make sure old data is lost you must perform `unlink and clear` to specific template on desired host.

[geirra]

When LLD is discovered all data is added to the host as regular items and stays there till the expiration date (30 days by default)! It does not matter whether you have changed LLD or unlinked the template.
To make sure old data is lost you must perform `unlink and clear` to specific template on desired host.

I dont see how is this is related to old data.
When the macro actually works but only at 1 item at time.

Just for the fun of it i unlinked and cleared the template and readded it. Still the same problem.

Only 1 trigger uses the correct macro, the rest uses the default macro

[glebs.ivanovskis]

Probably you are facing this bug.