# URL Monitoring URL monitoring plays a critical role in ensuring the availability and performance of web services and applications across different geographic locations. This functionality enables users to specify which URLs to monitor and designate monitoring locations worldwide. It also ensures comprehensive visibility into the accessibility and responsiveness of critical online resources, facilitating proactive maintenance and enhancing user experience. ### Configure URL Monitoring in IT-Conductor To configure URL monitoring in IT-Conductor, follow the instructions below. #### Add New URL for Monitoring 1. Visit [service.itconductor.com](https://service.itconductor.com/) and enter your login credentials. 2. Navigate to **Dashboards → Administrator** to access the **Administrator's Dashboard**. 3. Locate the **URL Monitoring Locations** actions panel and click the title to access the complete list.

Figure 1: URL Monitoring Locations Actions Panel in Administrator's Dashboard

4. Click the **New URL Monitoring** button to start adding a URL.

Figure 2: URL Monitoring Actions Panel Page

5. Fill out all the necessary information in the **New URL Monitoring** wizard. Once completed, click

to add the URL.

Figure 3: New URL Monitoring Wizard (New URL Monitoring Location Screen)

* **Name** - refers to an identifier for the URL being added. * **Description** - refers to any relevant information about the URL being added. * **Organization** - refers to an administrative structure that defines objects with a common goal or purpose. If you previously created an organization, please select it. * **Role -** refers to the environment where the URL will be used. * **Site** - refers to a logical object that describes a particular area or location, depending on the context in which it is used. * **Gateway** - allows communication between the customer's site network and the IT-Conductor cloud platform. See [Gateway Setup](https://docs.itconductor.com/user-guide/setup/gateway-setup) for more details. * **Scheme -** specifies the protocol used for the URL (e.g., HTTP or HTTPS). * **Host** - refers to the host of the URL being added. * **Port** - refers to the port number used to access the URL being added. * **Connection Timeout** - refers to the maximum time allowed to establish a connection before timing out. By default, this is set to 300 seconds. * **Enforce Certificate** - if checked, it determines whether the monitoring should enforce SSL certificate validation for HTTPS URLs. 6. A new URL Monitoring location will be added to the actions panel. The status will remain on **Ready** until an HTTP probe is added. 7. Click on the new URL name, and then click on the

**HTTP Probes**. Alternatively, you can click ![](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FyGm5t132ZvXjl6V4X25d%2FiconShow.gif?alt=media\&token=d5f127a9-9701-4728-b36f-24dbe2016447) and then

**Probes.**

Figure 4: Newly Added URL Monitoring in the Actions Panel Page

8. Click

**Create HTTP Probe** to create a new HTTP probe.

9. Fill out all the necessary information in the **Create HTTP Availability Probe** wizard. Once completed, click the **Finish** button to create the probe.

Figure 6: Create HTTP Availability Probe Wizard

* **Name** - refers to a descriptive name for the probe. * **Description** - refers to any relevant information about the probe being added. * **Owner** - refers to the user who's adding the new probe. * **Application** - refers to the name given to the URL in the previous step. * **Schedule** - sets the frequency or timing for executing the monitoring. You may choose from one of the schedules previously created in IT-Conductor. See [How to Define Operating Schedules](https://docs.itconductor.com/reporting/scheduling-reports#reportscheduling-definingandoperatingschedules) for details. * **Planned Start Time** - refers to the scheduled start time for the monitoring task. * **Time Windows Begin** - refers to the beginning of the time window during which the monitoring can be executed. * **Time Windows End** - refers to the end of the time window during which the monitoring can be executed. * **Repeat** - specifies that the task should be repeated or executed only once if checked. * **Repeat Interval** - refers to the time interval between repeated executions of the monitoring task. By default, this is set to 15 minutes. * **HTTP Method** - determines the HTTP method for the request (Get, Post, Delete, Head, Put). * **URL** - refers to the URL of the web service or application to be monitored. * **Preserve Query** - when enabled, this option ensures that the full query string in the specified URL is retained during the probe request. * **MIME Type** - defines the expected MIME type of the response from the URL. * **Allowed Status** - specifies the HTTP status codes considered acceptable for a successful response. By default, this is set to 401. * **Follow Redirect** - determines that the monitoring should follow HTTP redirects if checked. * **Parse Results** - determines whether to parse and analyze the content of the response. 10. Wait for the HTTP Probe status to turn to **Waiting.**

11. Navigate back to the URL Monitoring Actions Panel Page. The created Monitoring Location should be in the **In-Progress** state. 12. Navigate to the service grid and verify if the URL and probe were added under the **URL Monitoring** node. Alternatively, you can click ![](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FyGm5t132ZvXjl6V4X25d%2FiconShow.gif?alt=media\&token=d5f127a9-9701-4728-b36f-24dbe2016447) and then

**Grid** to navigate to the URL Monitoring service grid.

{% hint style="info" %} **Note:** Please allow 5-15 minutes for the new URL and probe to show in the service grid. {% endhint %} ### Monitor URL Locations in IT-Conductor To view the availability, response time, and status code metrics of a monitored URL, locate the **URL Monitoring** node in the service grid.

Figure 9: URL Monitoring Node View in the Service Grid

#### **URL Monitoring Key Metrics** * **Connection Failures** - refer to the events where attempts to establish a connection are unsuccessful. * **Missing Account** - refers to the absence of a required user account or resource within the URL location. #### **HTTP Probe Key Metrics** * **Availability** - refers to the operational state and accessibility of the HTTP probe. * **Response Time** - refers to the duration (in msec) taken for the webserver to respond to the request. * **Status Code** - indicates the HTTP status code returned by the server, providing information on the success or failure of the request. {% hint style="info" %} **Note:** All metrics will not show data when the URL is unavailable. {% endhint %} To access a historical view of each of these metrics, click

and a pop-up chart will be displayed.

Figure 10: Availability Chart in Service Grid

### Video {% embed url="" %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.itconductor.com/user-guide/monitoring/general/url.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.