I'm configuring Zabbix 3.0 to monitor a bunch of my customer's websites. I stumbled upon a conceptual issue.
I like to implement processes to be flexible, therefore I created Web scenarios in a Template, not a Host. But then I started scratching my head because something didn't feel quite right.
As we know, Web scenarios are executed by Zabbix server itself and not by any agent on any Host.
So, now I have a template with 8 web scenarios. The template by itself doesn't run the web scenarios, of course. I have to link it to some host... but which one? And what's the point to add Web scenarios to a host at all, if the host itself does not run them?
Also - what will happen if someone accidentally adds my template to multiple hosts? Will Zabbix start executing those Web scenarios once for every host, spamming the servers with multiple parallel requests?
So, I'm not sure what is the recommended way (best practice) here. Where should web scenarios be attached to, conceptually? If there is not strict well-defined conception behind that, then what would be the best workaround to make web scenarios execute without accidentally duplicating the requests?
I like to implement processes to be flexible, therefore I created Web scenarios in a Template, not a Host. But then I started scratching my head because something didn't feel quite right.
As we know, Web scenarios are executed by Zabbix server itself and not by any agent on any Host.
So, now I have a template with 8 web scenarios. The template by itself doesn't run the web scenarios, of course. I have to link it to some host... but which one? And what's the point to add Web scenarios to a host at all, if the host itself does not run them?
Also - what will happen if someone accidentally adds my template to multiple hosts? Will Zabbix start executing those Web scenarios once for every host, spamming the servers with multiple parallel requests?
So, I'm not sure what is the recommended way (best practice) here. Where should web scenarios be attached to, conceptually? If there is not strict well-defined conception behind that, then what would be the best workaround to make web scenarios execute without accidentally duplicating the requests?