Configuring Tests in Global Service Monitor
Applies To: System Center Global Service Monitor
Here are some key concepts and strategies to be aware of as you use Global Service Monitor:
You can do most of your work with Global Service Monitor on the Global Service Monitor landing page. Here you can open the Web Application Availability Monitoring template or the Visual Studio Tests template to configure tests, update the proxy server and renew the certificate if you change the proxy server, and stop your Global Service Monitor subscription. Additionally, you can view active alerts and view tests state from this page. To open the Global Service Monitor landing page, in the Operations Manager console, in the navigation pane, click Administration, and then click Global Service Monitor.
The Global Service Monitor landing page
Global Service Monitor can monitor applications in addition to individual URLs. Your tests can be authored to optimize for application monitoring or vertical application feature monitoring. For example, a website shopping experience is a vertical application feature. Or, you can monitor horizontal application features, such as all home pages on a site.
Give your tests friendly names that you can easily recognize when you monitor them. These names are displayed in state views and alerts.
Web Applications State is a defined as the worst of rollup of individual tests for each template that is run. You can use overrides to change what is displayed.
Validate each internal test configuration by clicking Run Test before exiting the Add Monitoring Wizard so that you can check that the response that you get is the one that you expect for internal watcher nodes.
You cannot validate test configurations from external locations.
If you are monitoring a vertical website or an application, you can focus alerts on application state by setting up a summary alert for an application, rather than choosing to receive an alert for each URL test for an application. This will reduce the number of alerts you receive and keep the focus of your alerts the overall state of the application. You can further reduce alerts by set the threshold for how many failures you want to have before receiving an alert. Together, these two approaches will focus your alerts on what is most important to you: how well the application is running.
Comparing monitoring types
Operations Manager has three management pack templates that can be used monitor web applications.
|Monitoring template||When to use||Global Service Monitor Subscription|
|Web Application Availability Monitoring||- Have to know the availability of a web application
- You have to see how your application webpages respond when they are accessed from external geographic locations around the world
- You are not looking to monitor multi-step transactions
|Visual Studio Web Test Monitoring||- Have to know the availability of a web application and more details
- You have to monitor your applications by using Visual Studio web tests that are running from external geographic locations around the world
- You do have to monitor multi-step or authenticated transactions
|Web Application Transaction Monitoring||Have to monitor intranet applications from internal locations. The monitored applications cannot be accessed from the Internet||Not required|