How to create an agentless HTTP metric for monitoring a specific website

book

Article ID: 181416

calendar_today

Updated On:

Products

Monitor Solution Monitor Solution for Servers Monitor Pack for Servers

Issue/Introduction

 

Resolution

The purpose of this document is to demonstrate how to create an agentless HTTP (Hyper Text Transfer Protocol) metric for monitoring a specific website with Monitor Solution for the Symantec Management Platform (SMP).
An agentless HTTP metric is used for checking the availability for monitoring a specific website
For the purposes of this document, the following environment and technologies are being used:

    A simple client/server environment.
    Client is running Windows 7 (64 bit) and the server is running SMP 7.1 SP2 with Windows Server 2008 R2 Enterprise (64 bit).
    The Windows 7 Client will act as the web server which is running WAMP Server (64 bit) 2.2E
    WAMP Server 2.2E includes the following technologies: Apache 2.2.22, Mysql 5.5.24, PHP 5.3.13, XDebug 2.1.2, XDC 1.5,  
    PHPMyAdmin 3.4.10.1, SQLBuddy 1.3.3, webGrind 1.0.
               
PLEASE NOTE: WAMP is not a Symantec product and there are many other web server applications that provide an equal service. This document is using WAMP for exemplary purposes only.
               
Steps to create the agentless HTTP metric for monitoring a particular website:

  1. Install WAMP Server on the client machine or an equivalent web server application.
  2. On the SMP server open Internet Explorer and browse to http://localhost/altiris/console.
  3. Browse to: Home > Monitoring and Alerting.
  4. From here on the left hand side of the screen in the directory tree view expand Monitor > Policies > Monitor Policies.
  5. If desired, create a custom folder for storing policies.  To create a folder, right click the Monitor Policies directory and select new folder and give it a name.  Note:  A policy can be created in the Monitor Policies directory by following the same steps as in step 6 except in this case, right click on the Monitor Policies directory instead of right clicking the newly created folder.
  6. Right click on the newly created folder for the monitor policy and select New > Monitor Policy (Agentless).
  7. Give the policy a name by clicking the "New Monitor Policy" text at the top of the screen. For example:  HTTP Availability Test.
  8. Add a rule by clicking the blue plus sign below the rules tab. This will offer a prompt with “Select Rule“ window. 
  9. Click the yellow star that says “New” in the top left hand corner and select Metric.
  10. In the option to “Give the Metric Rule a Name” add a name such as "HTTP Availability Test"
  11. Give the Metric Rule if desired.  This field is optional.
  12. Next to Category, click the "Select category" link to select a category or create a new one by clicking the yellow star. In most cases, a new   one is more appropriate because the existing ones don't accurately describe the new metric. Note: The Category has no functional effect on the policy itself it is simply for organization and readability.
  13. In the Metrics section of the New Metric Rule window, click the yellow star to create a new metric.  This brings up the New Metric Evaluation window.
  14. Next to where it says metric, click the blue link that says Select metric. This brings up the Select Metric window.
  15. Click the yellow star that says “New” next to it and select HTTP. This brings up the New HTTP Metric window.
  16. Give the metric a name such as "HTTP Availability Test Metric."
  17. Give the metric a description as desired.  This field is optional. 
  18. Leave the fields labeled Polling interval and Thread Pool with their default values.

    Note:  Steps 19 and 20 are web server specific.
     
  19. Check the port number the particular web server is configured to run HTTP on. If the web server happens to be running on port 443 then click the SSL checkbox, otherwise leave it blank.
  20. This is where the web page to be monitored is specified relative to the particular web server's public HTML (Hyper Text Markup Language) directory.  The public HTML directory is the default directory that the web server makes available it's users. In this example WAMP uses a directory named WWW for it's public HTML folder so the Path field will be relative to the WAMP WWW directory.  For instance, the website being monitored in this example is located in the path "C:\wamp\www\testPage\index.html" on the web server. So to correctly enter the Path field, enter "/testPage/index.html".  In this instance the follwoing paths also worked: "/testPage/" and "/testPage".  The path will have to be adjusted accordingly based on the web server's directory structure and HTML file names.
  21. Leave the Return value field with the default value of HTTP status.
  22. After entering all the required fields on the New HTTP Metric window click OK.
  23. In the  “Select Metric window”.  Highlight the metric newly created (HTTP Availability Test Metric) and click OK.
  24. In the New Metric Evaluation page click OK.
  25. In the New Metric Rule page, the severity level can be set under the Actions section.  This is optional.  For test purposes leaving the severity level of Informational is fine.  Complete the metric as desired and click OK.
  26. In the Select Rule window select the new (HTTP Availability Test) and click OK
  27. In the new policy, create the desired targets.
  28. Next ensure that the policy is on by toggling the on/off button at the top right part of the screen.  It will say on and have a green light icon next to it when the policy is enabled.
  29. Finally hit the Save button and the policy is created.
  30. To start the HTTP availability monitoring immediately, Run “Update Configuration” on the Symantec Management Agent on the targeted machine's RMS server.