Uptime Configuration

On this screen, users can:

• specify the URL to be monitored
• define a custom name for the monitor
• select the check frequency
• add keywords for content checks
• configure HTTP request settings
• group the monitor with tags

These settings allow for different monitoring scenarios for various services.

URL and Monitor Name

When creating a monitor, the first step is to enter the URL to be monitored.

WebPixie will regularly check this address to measure the service’s availability and response time.

Optionally, a custom name can be defined for the monitor. This name can be displayed instead of the URL in the monitor list, making management easier, especially in workspaces with many monitors.

Check Frequency

The check frequency determines how often WebPixie will check the specified URL.

Shorter intervals allow for faster detection of outages.

WebPixie supports the following check frequencies:

• 30 seconds
• 1 minute
• 3 minutes
• 5 minutes
• 10 minutes
• 15 minutes
• 30 minutes
• 1 hour
• 6 hours
• 12 hours
• 1 day

For example, a critical payment service might use a 1 or 3 minute interval, while a less critical information page may be checked every hour or longer.

Keyword Check

Keyword check allows you to verify whether the page content contains specific words.

With this feature, you can detect unexpected situations in the content, even if the page is technically accessible.

For example:

• On a login page, you might expect the word “Dashboard” to appear
• On an e-commerce site, you can check for the message “Product not found”

This way, content errors can be detected more quickly.

Timeout

The timeout setting determines how long WebPixie will wait for a response to a request.

Services that take longer than the specified duration to respond may be considered inaccessible.

For example, if a page is expected to respond within 10 seconds, this value can be set as the timeout.

HTTP Status Codes

During uptime checks, WebPixie analyzes the HTTP status codes returned by the server.

Users can specify which status codes indicate that the service is operational.

Successful responses typically include the following codes:

• 200 — successful response
• 201 — resource created
• 204 — no content but request was successful

Tags

Monitors can be grouped using tags.

Tags allow users to categorize monitors and make them easier to manage by filtering on the uptime screen.

For example, tags like:

• production
• staging
• api
• payment

can be used to easily organize different services.

Creating the Monitor

After all settings are completed, you can create the monitor by clicking the Confirm button.

Once the monitor is created, WebPixie will start monitoring the specified URL and the monitor will appear in the uptime list.