08-30-2013 11:37 AM
I am trying to create a template that would deploy monitors in the correct folders.
I am hoping to create a template so when I deploy the template at the top level, SiteScope will know which group to deploy the monitors in.
I tried to create a template like this, however, I get a uniqueness violation because when I deploy the template for the 2nd time for other monitors, Sitescope says that the Groups with the exact name already exists therefore i get a uniqueness violation.
Any advice is very much appreciated.
09-01-2013 11:38 PM
Please can you send us/share the template are you trying to deploy?
Also, can you share the the steps you follow to deploy the template?
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution."
09-03-2013 09:05 AM
Thanks for the reply.
The attached file is a snapshot of the template i am trying to deploy.
So basically we are trying to separate all our servers and we currently have like 4 levels in the hierarchy.
So some of the servers may have the exact same hierarchy...meaning the exact same paths like level 1, level 2, level 3, level 4 may have the exact path and names for some of the hosts.
So lets say I want to deploy monitors A and monitors B separately that also have the exact same group names.
How can I do this in SiteScope through just one deployment rather than deploy the template multiple times?
Any advice on this is very much appreciated.
09-03-2013 09:08 AM
10-08-2013 02:13 PM
I too would find this useful... if you want to create nested groups via template it would be very nice to have.
In this case, the template always fails because it tries to create a new group called MiddleWareApp1 for Servername2, which already exists because that group was created when deploying Servername1
Here would be the CSV for that:
Variables: appname (MiddleWareApp1, 2), hostname (Servername1, 2)
MiddleWareApp1,Servername2 (this would fail, as MiddleWareApp1 already exists)
10-08-2013 10:50 PM
This is one of the features that I would have loved to have when we first setup our environment, but I don't think it exists to date.
Depending on number and solution date, you could
*group(which you probably already did) your serves by hierarchy in a list
*create the lowests hierarchy folder and deploy all servers ther via csv(which takes a second or two)
and then just cut/paste them over to create your full tree.
10-09-2013 07:08 AM
Yes, that is what we're going to have to do.. we also will put the name into the name of the monitor so that it is easy to identify which monitors go into which group... and then use global search and replace to remove the strings after the monitors are in their appropriate groups.
Either that or just leave them all in 1 giant group, and leave the 'appname' in front of the hostname in the monitor name... might look a little more messy, but it's easy.
It's really too bad that templates require a group.. if you could just pick the group and deploy directly into the group it would be a bit nicer.
12-03-2013 03:33 AM
I'm using this easy and 'tricky' technique to avoid "uniquess violation" for groups.
1rst I've set this parameter to "true" in master.config, it allows create monitors directly on templates and no groups are required to create when a template is defined
The "uniquess violation" still occurring if the Group name is fixed, but to avoid it I use to create groups during the template deployment. And then the single monitors are created under one single group
It allows me to create monitoring structures like
Because before the change of this parameter I was having the "uniquess violation" error for Group Names when the name was fixed on template, and when I used variables to automatically name the groups SIS created monitors like:.
monitor - 1
monitor - 2
Hope this helps
12-03-2013 07:20 AM
I may not fully understand the problem, but I have templates with somewhat complex nested groups and deploy them regularly. The group name contains a variable (the server's name). Using this method, I have deployed 800 servers in one CSV file without uniqueness issues. Each monitor also contains the the variable, so it will say:
ServerName (master group)
- ServerName - Metrics (group) + dependency to Availabiity monitor
- ServerName - EventLog (monitor)
- ServerName - PerfMon (monitor)
- ServerName - Availability (monitor)
ServerName is a variable (the only one for this template)
My VMware templates are more complex and have 3 group levels total since I put all guest machines "under" the host for dependency linking.
ESXiDCName (master group)
- ESXiHost1 (group)
- ESXiHost1 - Availability (monitor)
- ESXiHost1 - Metrics (group)
- ESXiHost1 - CPU (monitor)
- ESXiHost1 - Memory (monitor)
- ESXiHost2 (group)
- ESXiHost2 - Availability (monitor)
- ESXiHost2 - Metrics (group)
- ESXiHost2 - CPU (monitor)
- ESXiHost2 - Memory (monitor)
- ESXiHost Guests (group)
I use 3 variables for this template - ESXiHost1, ESXiHost2, and ESXiDCName for the datacenter name so it mirrors what vCenter looks like. This would be for a two-host HA deployment. Guests are added separately with a standard Windows/Linux template.
Anyhow.. when i deploy I just right-click on the location where I want this structure to build out. We put these into site folders which are basically root folders that contain everything for a site (servers, storage, etc).
I am sure it's not this simple - the comment about having SiteScope "know where to put" something may be where I am misunderstanding.