Define a Health Criteria for your web application Monitor Part III
W're almost at the end! :-) Only 3 steps left. First we have to define a healt criteria for our web appliction and after that we can create our distributed appliction that will drive ou service level dashboard.
Use the Web Application Editor to choose what conditions will cause an error or warning during a synthetic transaction. For the Service Level Dashboard, an error is equivalent to an availability exception, and a warning is equivalent to a performance exception. Availability exceptions will also affect performance reporting. You can also choose to generate an alert when the status changes. For example, if your transaction includes a request to a specific Web page, you can choose to generate an alert if the page is unavailable. This is done by changing the health status of the transaction when the HTTP status code is 404.
Synthetic transactions are created by recording a Web site or by manually creating requests. For more information about recording a Web site, see How to Capture a Web Application Recording in Operations Manager 2007. For more information about manually creating or editing individual requests, see
How to Create or Edit a Request in Operations Manager 2007.
To set health criteria for a request in a Web monitoring session
1. Open the Authoring pane.
2. Expand Management Pack Templates, and then click Web Application.
3. Select the object you want to edit, and then click Edit Web application settings.
4. In the Request Details pane, you can set criteria to generate an error or warning health state for the request. For example, select the Http Status Code check box, and then select Equals and 404 to change the status when the page is not found.
![clip_image002[1]](http://scug.be/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/scom/clip_5F00_image002_5B00_1_5D005F00_thumb_5F00_7F080B9C.jpg "clip_image002[1]")
5. If you want an alert generated when the health status changes, select the Generate an alert if any error criteria is met or Generate an alert if any warning or error criteria is met check boxes.
6. If you want the transaction to stop when an error or warning criteria is met, select the Stop processing the subsequent requests if any criteria is met check box.
7. Click Verify to test your changes.
8. After the changes are verified, click Apply, and then close the Web Application Editor.
Important Repeat this process for every monitor that you create.
Next we will create a distributed appliction to drive the service level dashboard.
Greetz,
Alexandre Verkinderen
http://scug.be/blogs