MonSpark Docs
  • 👋Welcome to MonSpark
  • Overview
    • 💡What Is Monitoring?
    • ✨Types of Monitoring
    • 🛠️Getting Started with MonSpark
  • Fundamentals
    • 🔔Alerting
      • 📒Integrations
      • 🚨Escalation Policies
    • ⚠️Incidents
    • 📣Status Pages
    • 🏅Summary
    • 🔍Auto Discovery
  • Website Monitoring
    • 💻What is Website Monitoring?
    • 🛠️Getting started with Website Monitoring
    • ⚙️Working With Monitors
      • ⏯️Pausing/Resuming Monitors
      • 🗑️Deleting Monitors
      • 💠Bulk Create
      • 📄Reporting
    • 📈Availability
      • Uptime Monitor
        • Uptime Monitor Create
        • Understanding Uptime Monitor Details
      • Ping Monitor
        • Ping Monitor Create
      • TCP Monitor
        • TCP Monitor Create
    • 🛡️Security
      • Domain Expiration Monitor
        • Domain Expiration Monitor Create
      • DNS Record Monitor
        • DNS Record Monitor Create
      • IP Blacklist Monitor
        • IP Blacklist Monitor Create
      • Whois Monitor
        • Whois Monitor Create
      • Subdomain Monitor
        • Subdomain Monitor Create
      • Port Discovery Monitor
        • Port Discovery Monitor Create
    • ✨SEO
      • Lighthouse Audits
        • Lighthouse Monitor Create
      • Sitemap Monitor
        • Sitemap Monitor Create
      • URL Monitor
        • URL Monitor Create
    • ⛓️Integrity
      • Text Monitor
        • Text Monitor Create
      • Screenshot Monitor
        • Screenshot Monitor Create
      • Cookie Monitor
        • Cookie Monitor Create
      • Technology Monitor
        • Technology Monitor Create
      • Source Code Monitor
        • Source Code Monitor Create
    • 🕐Cronjob Monitoring
  • Server Monitoring
    • 🖥️What is Server Monitoring?
    • 🛠️Getting Started with Server Monitoring
      • 🖥️Servers
      • ⏰Alarms
      • 🗃️Rules
  • Transaction Monitoring
    • 🔮What is Transaction Monitoring?
  • Extras
    • ⛑️Troubleshooting and Support
      • IP Whitelisting
    • ⁉️FAQs
    • 💬Appendix
Powered by GitBook
On this page
  • Create an Uptime Monitor with just 3 clicks!
  • Advanced Uptime Monitor Configurations
  • General Settings
  • Request Settings
  • Notification Settings

Was this helpful?

  1. Website Monitoring
  2. Availability
  3. Uptime Monitor

Uptime Monitor Create

PreviousUptime MonitorNextUnderstanding Uptime Monitor Details

Last updated 10 months ago

Was this helpful?

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!

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

General Settings

Target URL

The URL of the website you want MonSpark to monitor

You can use the "multiple mode" to create multiple monitors with the same configurations at once!


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.

This feature is particularly useful when the monitored website still returns a 200 (OK) status code in the event of an error


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.

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


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.

You can use this feature to monitor services that require login using bearer authentication.


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.


Tip

📈
💡