Meraki devices set host group grayed out

[tc-at-work]

Using the Cisco Meraki device by HTTP template, all the discovered devices are force-set to Application host group and cannot be changed. Is there no way to set which group these hosts are in?



Thanks

[markfree]

It appears that group is set on the "Devices discovery" LLD. You should be able to change the host group on the LLD hosts prototype configuration.

[tc-at-work]

It appears that group is set on the "Devices discovery" LLD. You should be able to change the host group on the LLD hosts prototype configuration.

Hmm, I’ve got a couple hundred Meraki devices, wouldn’t that change the group for each of them?

[markfree]

Yes, indeed.

[tc-at-work]

Hmm, I’ve got a couple hundred Meraki devices, wouldn’t that change the group for each of them?

That’s unfortunate, we’re currently evaluating Zabbix. This combined with the inability to set parent hosts (I’m aware of trigger dependencies, that’s far too much work for our number of devices just to prevent getting spammed because a site’s main FW went down) makes the product untenable.

Appreciate the input though!

[markfree]

You could try modifying the host discovery rule and creating different prototypes for your devices.

[cyber]

I have not used this template myself, I don't know what kind of info is returned from query... but for host prototypes you can also use a group prototypes, not just that hardcoded one. If there is some values in discovery, which are usable for hostgroups, then use them.. There seems to be "{#ORGANIZATION_ID}" I have no idea, what it actually means, but it creates some thoughts..