zabbix 7 does not accept anymore LLD macros in delay parameter

[giotto69]

Hello all,
we are no more able to use LLDMacros in items delay parameter in Zabbix 7.
It complains it is not a correct time format; of course it is not since it's a macro of the form {#LLDMACRO}.
Documentation states that LLD Macros are supported in delay parameter but it seems to be no more true in 7.
does anyone have info about that?

Giorgio

[guytarr]

Asynch polling has nothing to do with LLD being there or not... It is the way how pollers work, but all the discovery is still run before all that, all he items are prepared before all that..

back to question... yes, docs say LLD macros are supported in item update interval field. There is a footnote for that...

Is this, how your time intervals are set up?

I found this ticket, it's just a small UI bug

Until a fix, we can force through API or SQL

We use files that Zabbix reads on the servers to delegate the creation of certain monitoring types by LLD and the frequency is defined by the team that populates the file (so 2m, 1h, 5m etc...) : for example, a file with the targets, port and frequency (and some others things usefull for the trigger and tags) that will generate net.tcp.port items

You're right : this has nothing to do with pollers (async or not) in our case

[guytarr]

Same problem here. It's just an UI issue, forcing an ldd macro with SQL and it works !

[mrnobody]

New pollers have been created to use walk and get items (like in cmd line tests), with dependent items (Asynchronous data collection \m/) to improve this kind of feature. So, LLD may be deprecated (7.0>) and it's first signal of that a see.

Would you/we/us recreate your/ours templates to use new faster and furious features?
Or stay on "KISS" LDD and force it usage in DB (Synchronous data collection)?

Choose your destiny.

[cyber]

Asynch polling has nothing to do with LLD being there or not... It is the way how pollers work, but all the discovery is still run before all that, all he items are prepared before all that..

back to question... yes, docs say LLD macros are supported in item update interval field. There is a footnote for that...

Footnotes
¹ In the fields marked with ¹ a single macro has to fill the whole field. Multiple macros in a field or macros mixed with text are not supported.

Is this, how your time intervals are set up?

[guytarr]

Asynch polling has nothing to do with LLD being there or not... It is the way how pollers work, but all the discovery is still run before all that, all he items are prepared before all that..

back to question... yes, docs say LLD macros are supported in item update interval field. There is a footnote for that...

Is this, how your time intervals are set up?

I found this ticket, it's just a small UI bug

Until a fix, we can force through API or SQL

We use files that Zabbix reads on the servers to delegate the creation of certain monitoring types by LLD and the frequency is defined by the team that populates the file (so 2m, 1h, 5m etc...) : for example, a file with the targets, port and frequency (and some others things usefull for the trigger and tags) that will generate net.tcp.port items

You're right : this has nothing to do with pollers (async or not) in our case

[giotto69]

Hi guys
thanks for your feedbacks.
One more workaround to assign macros is exporting the tempate with a "correct" time unit, change the template (json , yaml or whatever) and re-import.