Docs

Create a monitor

Learn how to create a monitor from the dashboard and what every field and default does.

This page explains how to create a monitor from the dashboard and what every field does. The same fields are available over the REST API and MCP.

#Prerequisites

  • A project. Every monitor belongs to one.
  • The owner, admin, or member role in that project. Viewers cannot create monitors.
  • A target UptimeX can reach from the public internet. Private addresses, localhost, and hosts without a dot are refused.

#Create a monitor

  1. Open the project and choose New monitor.
  2. Choose a check type. HTTP, Keyword, Heartbeat, and Port are on every plan. API, DNS, and Scheduler need Pro or Team. For what each type checks, see Check types.
  3. Give the monitor a name of up to 16 characters. You can change it later.
  4. Enter the target: a URL for HTTP, Keyword, API, and Scheduler, a host for Port, or a domain for DNS. A heartbeat has no target, since your job calls UptimeX.
  5. Set the interval and any options you need, then choose Create.

For HTTP, Keyword, and API monitors, Test check runs one check against the form as it stands and shows the result without saving anything.

The first check runs as soon as the monitor is created, so the page shows a real status within seconds. A heartbeat waits for its first ping instead, and a scheduler runs at its next scheduled slot.

Monitor limits

An account can have 5 monitors on the free plan, 30 on Pro, and 50 on Team, across all of its projects. Paused monitors count.

#Fields for HTTP, Keyword, and API monitors

FieldDefaultNotes
MethodHEAD (GET for Keyword and API)HEAD, GET, POST, PUT, PATCH, DELETE, or OPTIONS. A monitor with content rules always uses GET or a write method, since it needs the body.
Check every5 minutes1, 5, 10, or 30 minutes, or 1 hour. 1 minute needs Pro or Team.
Request headersnoneUp to 4. Stored encrypted and never shown again. See Requests and rules.
Request bodynoneUp to 8 KB, with POST, PUT, PATCH, or DELETE only. Sent as JSON unless you set a Content-Type header.
Timeout10 s5, 10, 30, or 60 s. A check that takes longer is down.
Slow threshold1.5 s0.5, 1, 1.5, or 3 s. A check that passes but takes at least this long is slow.
Expected statusAutomaticAutomatic accepts any status below 400. Or choose a code, or enter one between 100 and 599, and only that code passes.
Follow redirectsOffOff treats a 3xx as a pass. On follows the redirect and judges the final response. Monitors with content rules always follow.
Check SSL certificateOffPro and Team. https URLs only. See SSL and domain expiry.
Check domain expiryOffPro and Team. Needs a target with a registrable domain.
Failure threshold31 to 5 consecutive failed checks before the monitor is confirmed down.
Recovery threshold11 to 5 consecutive passing checks before it is confirmed up again.

Keyword monitors add content rules under Content match, and API monitors add JSON assertions. Both are explained in Requests and rules.

#Fields for the other types

TypeFields
HeartbeatExpected every: how often your job should ping. Grace: how late a ping may be before the monitor goes down, 1, 5, 10, or 30 minutes (1 minute by default).
SchedulerMethod (POST by default, or PUT, PATCH, DELETE) and Run every. Headers, a body, and the timeout can be set after creation in Monitor settings.
PortPort number, Check every, and under Advanced settings the timeout and the two thresholds. The host can be a hostname or a public IPv4 address.
DNSRecord type (A by default, or AAAA, CNAME, MX, TXT, NS), Check every, and an optional expected value. The target must be a hostname, not an IP.

#After you create it

Open the monitor to watch its status, uptime, response time, and activity, or to pause it. Every field except the type can be changed later from Monitor settings. For what happens from here, see The monitor lifecycle.

#What's next?