Export (0) Print
Expand All

Global Service Monitor

Updated: January 15, 2013

Applies To: System Center Global Service Monitor

System Center Global Service Monitor is a cloud service that provides a simplified way to monitor the availability of external-web-based applications from multiple locations around the world. Importantly, Global Service Monitor monitors applications from the perspective of the customers who use them. Because Global Service Monitor monitors from locations that are correlated to customer geographies, application owners can gain insight into customer experiences in addition to the separate problems related to external factors, such as Internet or network problems, from application or service problems. The Global Service Monitor monitoring experience focuses on the application instead of the infrastructure or individual URL.

Global Service Monitor integrates with the Operations Manager console so that you can monitor external- and internal-facing web applications in the same place you monitor other applications.

Global Service MonitorMonitoring Capabilities

With Global Service Monitor, the Operations Manager console integration lets you monitor web applications from both internal and external locations. In Global Service Monitor, you can use your management group and obtain access to agents in the cloud provided by Microsoft. This lets you monitor web applications from 15 locations and then report back to your management group. You can also use your own agents as watcher nodes to monitor internal locations and applications.

Two kinds of monitoring

Global Service Monitor is set to provide you a maximum number of tests for the two monitoring types. These are the Web Application Availability monitoring that monitors single URLs, and Visual Studio Web Tests monitoring that lets you to run multi-step, authenticated web tests from Microsoft-provided agents in the cloud. In the version of Global Service Monitor, Visual Studio Web Tests can be run from 15 external locations.

noteNote
To view a web test result that you download from Global Service Monitor, you must be running Microsoft Visual Studio Ultimate 2012 or Visual Studio Ultimate 2010 with these additions:

  1. Test controller crashes or stops responding when you run web tests in Visual Studio 2010 if the test results are large

  2. Install this hotfix: http://hotfixv4.microsoft.com/Visual Studio 2010/sp1/DevDiv954543/40219.363/free/441527_intl_i386_zip.exe

Test Maximums and Locations

For Web Application Availability monitoring, a test is defined as one URL from one location. For Visual Web Tests monitoring, a test is defined as one .webtest file from one location. For both monitoring types, the total number of tests equals the number of tests that you monitored multiplied by the number of locations from which you monitor. You can run each test as frequently as you want at intervals of 5 minutes or more. One test every 5 minutes is the minimum supported test interval for Global Service Monitor. Only the maximum supported number of tests will remain monitored. Additional tests will not be monitored and tests that exceed the maximums are displayed as “not monitored” in the Operations Manager console. Additionally, you will receive alerts related to exceeding the maximum supported number of tests. To view these alerts, in the Operations Manager console, in the navigation pane, click Monitoring, expand Operations Manager, and then click Global Service Monitor.

noteNote
Test maximums and locations are subject to change.

To see how many tests you have scheduled, in the Operations Manager console, in the navigation pane, click Administration, and then click Global Service Monitor.

Test parameters for Global Service Monitor Web Application Availability monitoring tests include the following:

  • Total tests = the number of tests multiplied by the number of locations.

  • Trial subscription: Total tests cannot exceed 25 per subscription (10 tests maximum for each location).

  • Paid subscription: Total tests cannot exceed 25 per subscription (10 tests maximum for each location).

  • Minimum interval per tests must be greater than or equal to 5 minutes.

  • Global test timeout: 30 seconds.

Test parameters for Global Service Monitor Visual Studio Web Tests monitoring tests include the following:

  • Total tests = the number of .webtest files multiplied by the number of locations.

  • Trial subscription: Total tests cannot exceed 25 per subscription (3 tests maximum for each POP location).

  • Paid subscription: Total tests cannot exceed 25 per subscription (3 tests maximum for each POP location).

  • Minimum interval per tests must be greater than or equal to 5 minutes.

  • Maximum number of requests per web test: 100.

  • Maximum web test file size: 100 kilobytes (KB).

  • Download/Response size limit per request: 500 KB.

Subscriptions per tenant:

  • Trial subscription: 1

  • Paid subscription: 5

With Global Service Monitor, you can test from 15 locations by selecting from the following:

  • Australia: Sydney

  • Brazil: Sao Paulo

  • Europe: Amsterdam, London, Paris, Stockholm, Zurich

  • Russia: Moscow

  • Singapore

  • Taipei

  • United States: Chicago, Los Angeles, Miami, Newark, San Antonio

Important Things to Know

  • To use Global Service Monitor, you must have System Center 2012 – Operations Manager installed.

  • For Web Application Availability Monitoring, only public-facing URLs (that do not require authentication) are supported in provided locations. Internal-facing URLs that do not require authentication can also be monitored by using internal agents as watcher nodes in the network.

  • If you configure more than 50 tests for Web Application Availability and more than 45 tests for Visual Studio Web Tests, additional tests will not be run and you will not be notified. The console displays tests that exceed the maximums as “not monitored”.

  • The web application name is part of the performance counter instance name. If you rename your web application, the performance counter instance names will also change. This causes data in the performance view to be split across the different counter names. Dashboards show only the latest values from the performance counter and the previous data is no longer displayed.

Global Service MonitorTopics

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft