ManageEngine® Applications Manager

HTTP URL Monitors

<< Prev


Next >>

HTTP URL Monitors


In an environment, where the downtime of any website applications and services can cause a negative impact on the business performance, problems must be accurately identified and solved.


Applications Manager acts as a continuous URL monitoring service that keeps constant watch over a specified URL or website page. They test the website applications and web services to ensure that they are functioning properly.

URL monitors verify the availability of specified, addressable, standard HTTP and HTTPS URLs. They scan the HTTP and HTTPS pages looking for a predefined keyword to check whether the website is available.

There are two ways of URL monitoring provided by Applications Manager.

The difference between the two types of monitoring is that URL Monitoring monitors single HTTP and HTTPS URL, whereas URL sequence monitors a set of HTTP and HTTPS URLs in sequence. Also, any HTTP and HTTPS URL can be monitored using URL Monitoring.

Please go through the following sections to know about the configuration details.


To configure for URL monitoring, follow the given steps:


Monitor display name, URL address, polling interval and timeout parameters are specified here

HTTP Configuration
Connection related parameters are specified here

Note: The content search is case-sensitive. If you provide 2 words, the content match is performed for the words separately. For example, if you specify the content as applications manager, the match is found for applications and  manager separately. If you need the content match to be performed for the complete text, specify the 2 words in quotes, example "applications manager"

Content Check

The criteria that the  content of the URL page should adhere to are specified here.  

Apart from the basic URL Monitoring, Applications Manager also provides you with advanced options that furnish effective and more flexible URL Monitoring. This is optional and you need to choose these options only if the HTTP/ HTTPS URL requires Form-based authentication.

  1. Provide the request parameters, if any. The request parameters must be provided as name=value pairs for Post and Get methods.
    For example, if you want to monitor a URL like, http://appmanager:9090/, then provide "?haid=1&type=UrlMonitor&method=getMonitorForm" as request parameter.

  2. Enter a keyword which when matches with the content in the URL must be notified of error in Error If Match field. Note: The search is case sensitive. Multiple keywords should be put within quotes. Otherwise, it will be treated as 'Any' one of the multiple keywords.

  3. Enter the Response Code details by choosing them from the combo box. By default, it is greater than 200. Hence the error will be notified once the criteria mentioned are met.

  4. Enter the time, in minutes, for which the URL monitor should wait for a page to complete downloading before timing out in Time out field.

  5. Check "If monitor detects error, re-try immediately to verify error", where the monitoring is automatically performed when it detects an error, i.e. when an error is detected, the monitor will immediately be scheduled to run again once.

  6. Provide the User name and password, if the URL requires Form-based authentication.

  7. Sometimes you may want to customize the default HTTP request header. You have the option to customize the "User-Agent" field. Check the Custom HTTP Headers and User Agent checkbox and enter the HTTP Header and User Agent in the text boxes. You may add multiple HTTP Headers and User Agents.



We support NTLMv1 and NTLMv2 authenticated URLs. To monitor NTLM authenticated URLs, copy the cryptix-jce-provider.jar from to <AppMgr Home>\lib\ext. Restart Applications Manager.

HTTP-URL Sequence Recorder (Transaction Recorder Tool)

The purpose of URL Sequence is to monitor multiple web pages of an online application. It checks pages with dynamically generated information enhancing interactive transactions such as logging into a login page, creating an account using a web form, instructing the application to perform some action, etc.


URL Sequencing starts with a specific URL such as the Login page and then followed by additional links/URL in it. The URL Sequence monitoring thus performs end-to-end verification of particular transactions helping you to troubleshoot any problems while monitoring.


Note: If you are connecting to an URL using a proxy server, then you must configure proxy to initiate the URL sequence monitoring. Refer to the Configuring Proxy section of Performing Admin Activities, for further details.

You can use the Transaction Recorder Tool to record all user online transactions in their exact sequence. These transactions will then be replayed at regular intervals of time and notifications will be sent when any error is detected.


Browse through the following topics to use the Transaction Recorder tool:


Getting Started

You must download and install the recorder tool to record the sequence of user transactions. Every step of the transaction will be captured and recorded. You also can modify or edit your transactions.


Hardware/Software Requirements

The Transaction Recorder is developed using the Microsoft .NET Platform version 2.0.  This is the minimum software requirement. A minimum of 2 MB of disk space is also required for installing the software.


Download and Installation

Download the new Recorder and start the installation process. The installation wizard takes you through a four step process after which the Recorder will be started:




Recording a New Transaction

After installing, the Transaction Recorder can be accessed under All Programs in Windows Start Menu. You can record a new transaction following these steps:




Modify an existing transaction

You can modify an existing transaction


  • If you would like to set User Agent for monitoring URL sequence, add the following key in AMServer.Properties file located in your Applications Manager installation folder.

    am.httpclient.useragent=<Browser User Agent which you would like to set>

Example: am.httpclient.useragent=Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461; SV1)

Save the file and restart Applications Manager for the changes to take effect.


Monitoring Dynamic URLs:

Suppose your login page has hidden parameters that needs to be submitted while logging into your application and the value for the hidden parameter is different for each login request. In this case, the hidden parameter value in the login page needs to be fetched dynamically and passed to the subsequent URL.


For monitoring these kind of dynamic URL Sequences, you can use $<Parameter name> [eg., $sessionID = 12] in the Request Parameter text box of the URL. So, while monitoring the URL Sequence, $<Parameter name> will fetch the dynamic values and pass it to the next URL in the sequence.


While using the Recorder tool, you cannot specify the parameters in the Request Parameter text box, so instead, after adding the URL Sequence, go to corresponding URL's 'Edit Monitor' page and enter the parameters. Consider the following URL Sequence :

In the above example access_token is a dynamic parameter whose value changes every time we login. In order to monitor the above sequence, follow the below mentioned steps :

So for every polling interval Applications Manager will search for this dynamically generated parameter and it will replace it.


See Also

Monitor Information - HTTP URL Monitors | Create Other New Monitors

<< Prev


Next >>

File Directory Monitor

Java Runtime Monitor