A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
Use SCOM’s Web Application Availability Monitoring template for URL uptime and response-time checks; use Web Application Transaction Monitoring instead when the test must simulate actions such as signing in or navigating multiple pages.
Configure basic website monitoring
- Open the Operations Manager Operations console.
- Go to Authoring → Management Pack Templates → Web Application Availability Monitoring, and start the template wizard.
- On General:
- Enter a descriptive test-group name.
- Select a destination management pack—preferably a dedicated, unsealed custom management pack.
- Choose the name carefully: after saving, it cannot be renamed without deleting and recreating the template.
- On What to Monitor:
- Enter a friendly website name.
- Enter the complete URL, including
http://orhttps://. - Multiple sites can be pasted or imported as
Name, URLpairs.
- On Where to Monitor From:
- Select Add/Remove.
- Choose one or more Operations Manager agents or resource pools as internal monitoring locations.
- Select locations that have DNS and network access to the website.
- On View and Validate Tests:
- Select each location and choose Run Test.
- Check the returned HTTP status, DNS resolution time, and total response time.
- If necessary, select Change Configuration to adjust frequency, timeout, accepted status codes, redirects, HTTP method, headers, request body, or proxy.
- Complete the wizard and save the configuration. The template supports both internal and externally reachable URLs. ^1^
By default, SCOM tests every 10 minutes, uses a 45-second timeout, and alerts after one failure when the HTTP status is 400 or greater. It also collects response time, DNS resolution time, TCP connection time, time to first byte, download time, and other performance measurements. Adjust these defaults if a single transient failure should not generate an alert. ^1^
View the results
In the Operations console, open:
- Monitoring → Application Monitoring → Web Application Availability Monitoring → Web Application Status for overall status.
- Test State → right-click a test → Open → Health Explorer for individual monitor health.
- Web Application Status → right-click an object → Open → Performance View for response-time and related counters. ^1^
If only one monitoring location fails, investigate that location’s DNS, proxy, firewall, or route. If every location fails, the website or its shared dependencies are the more likely scope of the problem.
When transaction monitoring is required
Choose Web Application Transaction Monitoring when monitoring must validate functionality rather than only a URL response—for example:
- Sign in with a test account.
- Browse through several pages.
- Submit a search.
- Validate returned HTML.
- Measure the performance of the complete request sequence.
Requests originate from watcher nodes. Each watcher node must have the Operations Manager agent installed and must be able to reach the target website; the website itself does not need a SCOM agent. ^2^
For HTTPS sites, certificate errors are not ignored by default. Correcting an invalid certificate is preferable; if monitoring a site that intentionally lacks a valid certificate, SCOM also provides an Ignore Server Certificate Errors option in Web Application Properties. ^3^
References