generic

Fine tuning of thresholds on discovered hosts can be done using user macro context. Trigger prototype will look like:

{host:item.last()} > {$THRESHOLD:"{#DISCOVERED.HOST.NAME.OR.WHATEVER}"}

Then you can set baseline {$THRESHOLD} for all discovered hosts and {$THRESHOLD:foo}, {$THRESHOLD:bar}, etc. for hosts "foo", "bar", etc.

+1 Macros should be editable for discovered hosts as well. Otherwise, this feature is hardly useful for enterprise environments. Unfortunately, user macro context is not practical for this because the fine-tuning still has to be done in the VMware templates. As soon as you have several 100 or 1000 user macro context objects, it is not easy to manage. Especially since a simple user (and not a Zabbix administrator) hardly understands this procedure, if at all. And if you don't want Zabbix users to be able to edit templates, this workaround won't work anyway.

From a user's point of view, it is difficult to understand why discovered hosts by network or Zabbix agent discoveries can be modified, but host prototypes by a VMware discovery cannot. There will certainly be a technical reason for this, but the behavior should still be identical everywhere.

I think the same should go with tags - currently you can't add tags to discovered hosts. Again this is often needed in large environments where tags are bringing a lot of logic into 3rd party integrations.

I agree, this should be implemented for both tags and macro's. VMWare monitoring especially is now in a state where it feels like you are locked into a position where the only way to override stuff is by creating multiple templates.

For example, if one had a test VMWare environment and wanted to only get production level notifications. Two templates would need to be made and maintained. One with no tag or the tag:test and another with tag:production.

Is it possible to use templates with external checks {HOST.NAME } for output to the map?

"Unknown": the output in such cases is a very common problem, since macros are not revealed on maps. How to solve it? I would like to create one template per nodes, rather than creating separate data elements.

Agree with @gofree. I think it's useful with tags as much as with macros.

Similar feature request for tags, ZBXNEXT-7591.

Just a quick status update. This functionality will be available in Zabbix 6.4. It could be possibly implemented earlier in Zabbix 6.2, depending of the final release date.

Dear DevTeam,
-I have tested this feature on Zabbix 6.2beta1 but it seems that Zabbix is not able to expand the LLD Macro inside the Hostprototype TAG and Macro.
Macro section

Tag section

-
I leave the comment only to show how much I'm a monkey was my fault on JSONPATH syntaxes...
When you work with the MACRO you have to pay a lot of attention and follow the right guidelines.

PS: Why the "TAG" tab do not show the number of tags like we can have for Macro?

dimitri.bellini, this feature is not implemented yet. It is too early for any testing.

@Alexei I got you, thanks so much

Implemented in:

• 6.2.0rc1 (master) 02ae9967c9a

Documentation updated:

• What's new
• Host prototypes

Updated API documentation pages:

• host.update
• usermacro.object
• usermacro.get
• usermacro.update
• Appendix 2. Changes from 6.0 to 6.2

Documentation updated:

• What's new
• Host prototypes