Hello,
I've wrote patch that add support of templates for web monitoring, i.e. with it web scenarios copied from template to hosts which linked to that template, updated when scenario changed in template and so on. Like items, triggers and graphs.
I think this is useful there are situations when same web software installed on many sites and there is no point to create separate scenario for each, when only one difference is host name.
The main changes are in frontend, but there are small bits in server code which add to user macros in scenario two predefined: {HOSTNAME} and {IPADDRESS} which replaced by dns name and ip address of host accordingly. This macros can be used in url substitution and without them there is a little meaning in templates for web scenarios.
Also patch change db schema by adding column templateid to table httptest.
And there is some limitation in my patch: host items that created by web scenarios (like Download speed for scenario.....) not linked to corresponding items in template.
Linked only web scenarios itself. Despite of that items in hosts normally added, deleted, updated than web scenarios in template changed. Linking of items is possible, but it complicated code and created double relation that AFAIK not good according to relation database theory.
So I think better solution is to block direct changing items related to web scenarios from frontend. I think this is good idea not only when templates used but for all items created by scenarios.
But in my patch there is no such blocking right now.
Patch against svn revision 6121.
I've wrote patch that add support of templates for web monitoring, i.e. with it web scenarios copied from template to hosts which linked to that template, updated when scenario changed in template and so on. Like items, triggers and graphs.
I think this is useful there are situations when same web software installed on many sites and there is no point to create separate scenario for each, when only one difference is host name.
The main changes are in frontend, but there are small bits in server code which add to user macros in scenario two predefined: {HOSTNAME} and {IPADDRESS} which replaced by dns name and ip address of host accordingly. This macros can be used in url substitution and without them there is a little meaning in templates for web scenarios.
Also patch change db schema by adding column templateid to table httptest.
And there is some limitation in my patch: host items that created by web scenarios (like Download speed for scenario.....) not linked to corresponding items in template.
Linked only web scenarios itself. Despite of that items in hosts normally added, deleted, updated than web scenarios in template changed. Linking of items is possible, but it complicated code and created double relation that AFAIK not good according to relation database theory.
So I think better solution is to block direct changing items related to web scenarios from frontend. I think this is good idea not only when templates used but for all items created by scenarios.
But in my patch there is no such blocking right now.
Patch against svn revision 6121.