The Alert Templates window allows you to configure generic alert settings that you can apply to servers and groups of servers in your organization. An event that causes a metric to no longer meet a condition or to exceed a threshold signals SQLdm to raise an alert. Alert templates save you time and help you to avoid mistakes by simplifying alert configuration across your environment. SQLdm displays the default template name and description in bold text.
Applying an alert template to a monitored server overwrites all existing alert configurations. You can make any custom changes to the specific server's alert configuration once the template is applied. If you make a change to a template that is applied to a server, you must also reapply the template to that server using the Apply To button.
Servers are not permanently attached to an applied alert template. SQLdm does not propagate to the monitored server any changes made to the template unless explicitly applied.
A template allows you to apply the same alert configurations to more than one SQL Server instance. It helps you avoid simple mistakes such as transposing characters or leaving out metric details that could occur when you manually configure each server. Alert templates also help you roll out changes by making the updates in a single location and then rolling out the changes across your environment. If you are more interested in ad hoc alert configuration, remember that you can use a template to return a server to default settings if you make any changes that you later want to revert.
Access the Alert Templates window
You can open the Alert Templates window from the SQLdm Console menu bar by selecting Tools > Alert Configuration Templates.
Create a new alert template
Create a new alert template or edit the existing Default Template to suit your needs when alerting on your monitored SQL Server instances.
To create a new alert template:
- Select Tools > Alert Configuration Templates.
- Click New.
- Type a unique name and description.
- If you want to create a new template based on an existing template , select the name of the existing template from the Copy from list.
- If you want to use this new template as your default template , check Default Template.
- Click OK when done.
- If you want to apply this new template to your existing SQL Server instances , click Yes in the confirmation message box. If you do not want to apply your new template to any existing SQL Server instances at this point , click No.
- Configure your alert settings , and then click OK.
Change an existing template
SQLdm allows you to make changes to an existing alert template. Select the template from the list, and then click View/Edit. If necessary, you can delete any existing template except for the Default Template. To delete a template, select the template you want to delete, and then click Delete.
Apply template changes to a tag or server
Once you create a new template or make changes to an existing template, you should apply the updates to your tags or servers. Select the template from the list, click Apply To, select a tag or servers to which you want to apply the alert template, and then click OK. Note that if the template you are making changes to is already associated with a tag or server, these changes are not automatically applied when you change the template. You must use the Apply To button and select the appropriate tag or servers.
Set a template to use as the default
You can set an existing template as the default for SQLdm to apply to all new servers added without specifying an alert template. To designate a template as the default, click the template in the list, click Set Default, and then click OK. If there is only one template in your list, SQLdm uses this template as the default.
Apply alert templates to individual databases or disks within an instance
SQLdm includes the ability to apply some alert thresholds on a per-database or per-disk basis within an instance. When you create an alert template and include one of these alerts, you cannot select which database or disk to apply the alert to because that is unknown in a template. For that reason, these alerts apply to all databases and disks within the instance to which it is applied.