LLD non default hostgroup
First of all, I love Zabbix!
Hi guys/girls, perhaps its somewhere on this forum but i wasn't able to find it, its not in the default documentation.
We have created some scripts to discover hosts at the customer side trough a proxy. For each customer we create new host groups. So lets say we discover fibre channel switches at 2 customers (fcs). Then we want to add those switches to different host groups (obviously) for permissions purposes we dont want customer A to see the fcswitches of customer B (permissions are set by usergroup linked to hostgroup(s) not hostobjects itself).
Customer A switch 1 2 3 should go to hostgoup: A.FCS
Customer B switch 1 2 should go to hostgroup: B.FCS
This is done by using macro's in the discovery scripts... i know we generate them by {#CUSTNAME}.FCS and assign that as an "groups prototype" some nice json work and its done. Works like a sharm, however we are still forced to set a default group(s) (I think this is due to the fact you may not receive the macro in the json so its left without any group). Resulting each discovered host is part of 2 hostgroups. Now we are able to fix this by doing some sql query's on the background on the table hosts.groups however that is pretty unsupported
.
After this we give permissions to all hosts groups A.* to customer A and B.* to customer B. (by hand or some unsupported sql queries I wont mention all the table names ;-) ).
Ok long story, now the question: is it possible to not put discovered hosts to a "default" host group (for now we add them all to a default hostgroup all.customers.fcs but we dont want that).
Some background info: We just upgraded to zabbix-server 3.0 (yes we changed all 50 snmp discovery scripts already to the new format small detail for those who want to upgrade).
Also another question but I will put this in another thread but perhaps you guys can help me out. We use psk encryption form proxy servers and put this on all hosts as well (perhaps unneeded or twice?) however discovered hosts dont have/inerhit encryption and cannot be enabled manually (again I suppose some unsupported sql queries can fix this).
Hi guys/girls, perhaps its somewhere on this forum but i wasn't able to find it, its not in the default documentation.
We have created some scripts to discover hosts at the customer side trough a proxy. For each customer we create new host groups. So lets say we discover fibre channel switches at 2 customers (fcs). Then we want to add those switches to different host groups (obviously) for permissions purposes we dont want customer A to see the fcswitches of customer B (permissions are set by usergroup linked to hostgroup(s) not hostobjects itself).
Customer A switch 1 2 3 should go to hostgoup: A.FCS
Customer B switch 1 2 should go to hostgroup: B.FCS
This is done by using macro's in the discovery scripts... i know we generate them by {#CUSTNAME}.FCS and assign that as an "groups prototype" some nice json work and its done. Works like a sharm, however we are still forced to set a default group(s) (I think this is due to the fact you may not receive the macro in the json so its left without any group). Resulting each discovered host is part of 2 hostgroups. Now we are able to fix this by doing some sql query's on the background on the table hosts.groups however that is pretty unsupported
.After this we give permissions to all hosts groups A.* to customer A and B.* to customer B. (by hand or some unsupported sql queries I wont mention all the table names ;-) ).
Ok long story, now the question: is it possible to not put discovered hosts to a "default" host group (for now we add them all to a default hostgroup all.customers.fcs but we dont want that).
Some background info: We just upgraded to zabbix-server 3.0 (yes we changed all 50 snmp discovery scripts already to the new format small detail for those who want to upgrade).
Also another question but I will put this in another thread but perhaps you guys can help me out. We use psk encryption form proxy servers and put this on all hosts as well (perhaps unneeded or twice?) however discovered hosts dont have/inerhit encryption and cannot be enabled manually (again I suppose some unsupported sql queries can fix this).
Comment