An availability test is used to determine the health of an Enterprise Application (EA).
An Enterprise Application (EA) can be made up of 3 elements:
- Availability test
- Map
- Dependencies
To find out more about Enterprise Applications see How to create an Enterprise Application
This article describes how to configure an aviailability test. You can also manually set the health state of an application.
Only the availability monitors configured here roll up to be displayed as the health of the EA. These monitors test whether the application is actually available to the end user.
- Click the configure availability monitoring button.
-
Change the enable monitoring toggle button from off to on.
-
Select the type of availability monitoring you wish to configure:
- Simple URL monitoring - create a simple URL monitor
- Simple TCP monitoring - create a simple TCP monitor
- Custom PowerShell - use a PowerShell script to test application availability
- Existing monitoring - allows you to add any availability monitor or object that you already have in SCOM, for example Web application availability monitoring or Web application transaction monitoring.
- Complete the details required.
- Select a group of test clients (Watchers) from the test from drop down box (this is not required for existing monitoring because this will already have been configured in SCOM). This is where you want the tests to be run from, and should be physically close to the end users who will be using the application. This is simply a SCOM group where the name starts with
EAM_, see How to create Availability Test Groups.
The outcome of the chosen availability test will roll up to the overall health of the Enterprise Application. If you consider editing the rollup see How to edit Enterprise Application rollups.
Remember you can also manually set the health state of an application.
For a deep dive on Application Availability Monitoring features take a look at the v4 webinar (40 mins) Advanced Application Availability Monitoring.