Uptime Monitor Create
Last updated
Last updated
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.
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!
The protocol used for the requests when monitoring your website.
The monitor name is used to identify this specific monitor and is also utilized in notifications.
Determines the frequency of monitoring checks.
Used to categorize monitors for future grouping, you can either choose from existing tags or create new ones
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
Determines the location from which MonSpark monitors the provided URL
The request method used for the monitoring requests.
The timeout value for monitoring requests defines the duration within which the website must respond.
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
Specifies whether redirects should be followed, allowing for a direct check of the availability of your target URL.
Sets the preferred DNS server for resolving the IP address of the target URL.
Determines the status codes considered 'up' or 'down' based on your monitoring preferences.
Configures the request headers sent with the monitoring requests to the target URL.
Tip 💡
You can use this feature to monitor services that require login using bearer authentication.
Determines the escalation policies that will be applied to the monitor.
Allows you to test notification channels and preview the information you'll receive during an event.