# Uptime Monitor Create ## Create an Uptime Monitor with just 3 clicks! * Click on the "Create Monitor" button on the Dashboard and select the "Create Uptime Monitor" * Provide the URL and click the "Create Uptime Monitor" button to start monitoring! {% @arcade/embed flowId="GcWRGZtSDGpDSgAkCWHt" url="" %} While it's just as simple as that, we have tons of configurations we can apply to our monitors to get the best monitoring experience. Most of the time, default configurations will work fine, but sometimes you may need to adjust a few to fit your specific needs. *** ## Advanced Uptime Monitor Configurations {% @arcade/embed flowId="y5Ouwx6r7ESYhwMpw676" url="" %} ### General Settings #### Target URL The URL of the website you want MonSpark to monitor {% hint style="info" %} You can use the "multiple mode" to create multiple monitors with the same configurations at once! {% endhint %} *** #### Protocol The protocol used for the requests when monitoring your website. *** #### Name The monitor name is used to identify this specific monitor and is also utilized in notifications. *** #### Check Interval Determines the frequency of monitoring checks. *** #### Tags Used to categorize monitors for future grouping, you can either choose from existing tags or create new ones *** #### Keyword Checks Enables strict monitoring for the absence or presence of a keyword within the given URL. {% hint style="info" %} This feature is particularly useful when the monitored website still returns a 200 (OK) status code in the event of an error {% endhint %} *** ### Request Settings #### Location Determines the location from which MonSpark monitors the provided URL *** #### Method The request method used for the monitoring requests. *** #### Timeout The timeout value for monitoring requests defines the duration within which the website must respond. *** #### Confirmation Count The confirmation count specifies the number of failed consecutive monitoring requests needed for the monitor to be marked as down. {% hint style="info" %} Note that the timeout and confirmation count work together to determine how long your website needs to be unreachable for it to be considered as down. For instance, a 30-second timeout and 3 checks mean the monitor will be marked as down if it remains unreachable for 90 seconds {% endhint %} *** #### Prevent Redirections Specifies whether redirects should be followed, allowing for a direct check of the availability of your target URL. *** #### Custom DNS Sets the preferred DNS server for resolving the IP address of the target URL. *** #### Up-Down Status Codes Determines the status codes considered 'up' or 'down' based on your monitoring preferences. *** #### Request Headers Configures the request headers sent with the monitoring requests to the target URL. {% hint style="info" %} Tip [💡](https://emojigraph.org/tr/light-bulb/) You can use this feature to monitor services that require login using bearer authentication. {% endhint %} *** ### Notification Settings #### Escalation Policies Determines the escalation policies that will be applied to the monitor. *** #### Test Notifications Allows you to test notification channels and preview the information you'll receive during an event. *** --- # 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.monspark.com/website-monitoring/availability/uptime-monitor/uptime-monitor-create.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.