Support & Documentation
Follow

Server Monitoring Templates

Server templates are used to create a consistent set of monitors, alert thresholds, and notification settings across all servers that inherit their settings from a given template. Generally speaking, you should usually start by configuring App monitors first, as those will apply to all servers that the given App is installed on (new or old). But, in the event that your focus is on Servers rather than Apps, Server Monitor Templates are a powerful feature that can ensure consistent monitor configuration.

Getting Started

Getting Started

In the Templates page, you will see that there are templates available for both Windows and Linux. You can start with one of the pre-populated ones created by Stackify and modify it, or create a new one from scratch.

You also may specify a default template, which is what will be applied to all new servers at time of agent installation.

A Note about Configuring Monitors

A Note about Configuring Monitors

For both Linux and Window server templates, you will be able to control when and what type of alert will trigger.  This will require you assigning a threshold to a monitor.  For example, if you set a threshold for an Alert to fire when CPU % reaches 98% or greater after 5 minutes, you will see a Critical Alert.  For more information on this, visit the Configuring Your First Monitors page.

Configuring a Windows Template

Configuring a Windows Template

A Windows template is broken down into several sections - Server Monitors, Performance Counters, Notifications, and the Selected Servers that the template is applied to.

Windows templates differ from Linux templates in that they offer Performance Counters as an option to be configured for all servers inheriting the template (Performance Counters don't apply in a Linux environment).

Windows Server Monitors

Windows Server Monitors

From Server Monitors, you can monitor Disk, File, IIS, Network, Processes, and Services. You can also monitor the health of your server using the System Health monitor (below).

Windows System Health

Windows System Health

System Health monitors include Top Processes, Server Availability, CPU, Memory, Agent Health, and (in the event of an Azure Role) Azure Server Status.

Windows Performance Counters

Windows Performance Counters

Just as you can configure Performance Counters on individual applications to be monitored on any server where the application is hosted, you can also set them up as standard monitors across all servers inheriting a template.

First, you will select your Performance Counter Category, which dictates what additional choices you need to make for your Performance Counter monitor.  Next, if applicable, you will have to choose the Instance of the Performance Counter to monitor.

Note: It is best to apply more generic server-related monitors, especially if there will be many servers on that template. If you apply a specific Performance Counter monitor to be applied by a template, only the servers that counter is available on will report data, while all other servers associated with the template will monitor that will report an error that the Performance Counter is not available.

Next, if applicable, you will have to choose the Instance of the Performance Counter to monitor.

Configuring a Linux Template

Configuring a Linux Template

Linux server templates work much like Windows server templates, with the difference being that there are Java MBeans as an option for each server, rather than Performance Counters.

Linux Server Monitors

Linux Server Monitors

From Server Monitors, you can monitor Disk, File, Network, and Processes. You can also monitor the health of your server using the System Health monitor (below).

Linux System Health

Linux System Health

System Health monitors include Server Availability, CPU%, Memory Used %, Top Processes, and Agent Health.

Java MBeans

Java MBeans

In the event that you have servers running a Java app server such as Tomcat, you can also add Java MBeans monitors based on a previously configured JMX connection (your best bet here is to configure a localhost connection where possible so that your connection can be used within a template and applied to each server, rather than using a server-specific JMX connection).

Notifications

Notifications

Notifications can be set for each Server Template.  Here you can choose a severity of when a notification group will be alerted.  The "Manage Groups" button above will take you to a screen to create a new notification group.  (To get more information on Notification Groups and how to add users to these groups, see the Setting Up Notification Groups article.

Selected Servers

Selected Servers

In the Selected Servers Tab, you can view which servers are using a certain template.  You can easily specify whether or not a server will use a certain template.  For example, by sliding the Windows 2008 server to the right (shown above) to start using this template, the server will inherit the monitoring configurations of the Windows Server Default Template and all previously configured monitors for that server will be overridden.  If a server is removed from a template, you will be prompted to associate the server with another template. (All servers must be assigned to a template).

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk