> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/start-here/systems-setup/url-monitoring.md).
# URL End-Point Monitoring
This document describes how to setup URL monitoring in IT-Conductor
1\. In the IT-Conductor main menu, navigate to **Dashboards > Administrator**.
2\. In the Administrator dashboard, locate and click **URL Monitoring Locations**.
3\. Click 
.
4\. Fill out the form and click after providing the details.
5\. A new URL Monitoring location with the "Initial" status will be created. Click on the **"HTTP Probes"** tool.
6\. You will be redirected to the HTTP Probes window. Click
7\. Fill out the form and click after providing the details.
8\. Wait for the HTTP Probe status to turn to "Waiting" and click the back button to return to the URL Monitoring Locations window.
9\. The created Monitoring Location should be in the "In-Progress" status to be active
10\. From the Monitoring Service Grid, you should see the URL monitored with its corresponding Availability, Response Time, and Status code:
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/start-here/systems-setup/url-monitoring.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.