host lld discovery group prototype problem

[gralech]

Hi there!

Using docker zabbix 5.0 psql + timescaledb
Cannot use group prototypes in different templates:
if one template create such group, others can't add host to it
Error message: Cannot create group: group with the same name "Services/NNNN" already exists.

[dimir]

Sorry, what's group prototypes? There is no such thing in Zabbix. Is it item or application prototypes?

[gralech]

There is, in Host prototypes - Groups

[gralech]

Also i'd like to create host only in one group.. subgroup of Services there - Services/{#NAME}, so later i can use Aggregated items on this group.. But i must choose existing group in * Groups field, so host will be in Services and in Services/NNNN group too

[dimir]

Oh, stupid me. This is what happens when you don't use LLD much. :-D
Looks to me the simplest would be to keep everything related to the same set of group prototypes in single template.

[gralech]

one lld discovery to rule them all? )
i need to create hosts for different services with attached different templates, one lld rule can do this?
ex: lld discovers redis, rmq, psql, etc... creates host from host prototype - for redis with attached redis template, for rmq - attached rmq template...

[dimir]

Yeah, I see now. I wonder why your {#NAME} resolves to the same value in different LLD rules?

[gralech]

i want to use aggregated checks, wich working on groups

[cyber]

I think host prototype is only able to attach certain template(s) to all it creates, it does not have any option to define template by some macro.
Maybe having a discovery per type is a way, one for redis, one for psql etc...Different filter to each, different template to each host prototype.

[cyber]

Put some default group there in *Groups... "Discovered Hosts" or something out of the box... Or just have some "hidden" group, which is not really visible to anyone.

[anykeymeister]

Hi there!

Using docker zabbix 5.0 psql + timescaledb
Cannot use group prototypes in different templates:
if one template create such group, others can't add host to it
Error message: Cannot create group: group with the same name "Services/NNNN" already exists.

Hello!
Having a exactly same problem. We have lots of same type hosts located in different places, which are created with LLD by pushing data from other server, and so much need ability to put them to different groups by location and topology (the way it connected to zabbix). Some of hosts may be located at the same place, but be connected with different gateways. Other ones located at different locations, but uses one gateway.
It might be fixed by manual addition of desired groups to hosts, but it is unable to add groups manually to discovered hosts.

Is it possible to edit LLD processing to it will create a host group if is not existed, but if the group already existed just add discovered host to it?

[hoppa]

https://support.zabbix.com/browse/ZBX-15012?jql=text%20~%20%22lld%20group%20prototype%22

Question to you guys here as I am walking straight into the same issue: the existing groups are created manually, right?
I'm now considering removing all manually created groups and let these be re-discovered by LLD. That should solve the riddle. Will "try this at home" later next week and will let you know the result.
Guess it's a kind of an ambiguous idea to have 2 sorts of Groups: those created manually and those created via LLD ...

[hoppa]

It's getting worse (from my perspective): it's indeed the case that if the Host Group is created via LLD, that this is a different Host Group from the ones created manually. Hence if I have 2 LLD running that would like to add the same Host Group with the same name that will not be possible.
The first creator of the Host Group is the only instance with that Host Group Name that will be created. Any attempt to create/access the same Group after this does not work :-(

[hoppa]

I've resolved this in my case by using TAGs ... I guess that Host Groups should be seen from a Zabbix functional level and not from an Application level ... sigh, but it works now for me (without going into API mode).