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.

Some features and limits mentioned on this page vary by plan. Visit our Pricing page to review the plans.

URL and Monitor Name

When creating a monitor, the first step is to enter the URL to be monitored. This can include a specific port or path, not just the bare domain.

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 check frequencies from 30 seconds up to 1 day:

• 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 Monitoring

Keyword monitoring allows you to verify whether the page content contains, or does not contain, specific words.

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

You can choose between two matching modes:

• Must contain — the check expects the given keyword(s) to be present. For example, on a login page you might expect the word "Dashboard" to appear.
• Must not contain — the check expects the given keyword(s) to be absent. For example, flagging the check as down if the page contains "Under Maintenance" or "Error".

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 Method

By default, WebPixie sends a GET request to the monitored URL. You can change this to a different HTTP method if the service you're monitoring expects it.

Custom Headers

You can add custom HTTP request headers to the check, for example to pass an API key, a custom Accept value, or any other header the monitored service expects.

Custom User-Agent

By default, WebPixie identifies itself with its own User-Agent when making requests. You can override this with a custom User-Agent string, for example if the monitored service blocks unrecognized clients or you want checks to appear as a specific browser or bot.

Follow Redirects

You can control whether WebPixie follows HTTP redirects (3xx responses) when checking the URL. When enabled, the check follows the redirect chain to its final destination; when disabled, the check evaluates the redirect response itself instead of following it.

HTTP Authentication

If the monitored URL requires authentication, you can configure it for the check. WebPixie supports Basic, Token, and Digest authentication methods.

Request Body

For methods that accept a request body, you can define one to send with the check. WebPixie supports Form Data, Raw, and JSON body types.

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

Monitoring Location

Checks can be run from multiple monitoring locations. If you don't select one, WebPixie automatically assigns a location for the check.

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.