Server templates are a fantastic tool for any of our customers with a large infrastructure. You can apply server template to server group so that all servers added to that group can share the same configuration. If you have a several servers that you would like to monitor in the same fashion, then a server template is the perfect way to accomplish this configuration quickly.
There are two ways to create a template; from scratch or from an existing server. Once you have created a template you can change the configuration whenever you like.
Choose the Server you want to base the template off of, and click the drop down in the Edit menu next to the server's name. At the bottom, you'll see Apply Template and Create Template. Select Create Template.
A window will open up that will let you choose your template name and which server group to place it in.
Once you click submit you will be taken to a new page; this is the server template's configuration page. To see all of the options for configuration you click the Edit button.
When you do, you will see a new window open up that lets you configure your templates, very similar to how you would configure a server.
The +Add button at the top of the control panel presents the Resource Catalog. Select the Template option.
Selecting Template will open a configuration window in which you name your template and choose a server group to store it under.
A new page will open that resembles a server page, but will not have the same options. For example, you will not be able to install the server agent because it is only a template, and not a server. You can add checks as you would on a server, by clicking +Add Monitoring and configuring the checks as you'd like them to be stamped out. Keep in mind, thresholds set will also be set when a template is applied to a server.
There will be no detected metrics, but you can select the checks you want to configure from the catalog. Remember that these should be basic checks, as they will be applied to multiple servers. So adding custom configuration is not recommended.
Often times naming across your infrastructure resources does not match exactly - whether it's network interfaces, disk drives/partitions, or database instances; however, they are often close enough that a simple pattern match will allow your to target your desired resource.
To help you deal with this ambiguity and minimize the amount of templates you have to manage, Panopta templates support two types of pattern matching - positive pattern matching and negative pattern matching.
Note: If you're creating a template off of a server, you will still retain the ability to pick resource options from a select list (if we've discovered any)
Positive pattern matching allows your to supply alpha-numeric characters and wildcards * to match against resources. For example, if your network interfaces were eth01, eth02, and nic01, you could match just the first two with eth*. When you apply the template, only the first two interfaces would have monitoring added.
Simply select "Pattern Match" when adding a metric to a template and enter your string accordingly. Note: this only applies to metrics that have options associated with them.
Negative pattern matching is as you'd expect, the opposite. By providing a pattern of eth* would lead to only the nic01 interface to have monitoring added to it.
One of the great benefits of using templates in hand with the Panopta server agent is continual discovery of new resources. Every hour, the Panopta server agent looks for new resources on the server - things such as drives/partitions, network interfaces, etc. By default, as we find these new resources, we'll run them through the metric rules you've defined in your template. If the new resources match any of the defined metric rules, we'll begin monitoring them according to your template definition.
To turn this feature off, uncheck the continual discovery option that appears in the apply template confirmation modal when applying the template to a server instance.
You can also use dynamic variables in your templates if needed, read our article about it here.
If you would like your template to be able to apply to servers with multiple IP addresses then you will want to use this field. Here you will invent your own labels for those multiple IP addresses. For example if you want this template to cover servers with both a public and a private IP address you could enter PublicIP, PrivateIP into this field. When applying a template with additional IP addresses you will be given the option to map the additional IP addresses of the template to the additional IP addresses of your server.
The Agent manifest file will also let you take advantage of this feature with Interface Mapping, to learn more about this you can see this article.
You can choose to select any monitoring location you would like for a template. This monitoring location will then over-ride the monitoring location of any server you apply it do. If you do not want this to happen select Not specified for your Primary Monitoring Location.
You can also choose to set your monitoring locations on any individual network service checks you may create for this template. This can be useful if, for example, you want to a template that does ping checks from multiple locations around the world.
Once you have created your server templates, then it is time to apply them to some servers.