Skip to content

Monitor Screens

Reference for the monitor create/edit form and detail screen. All values are also validated server-side.

Create / Edit Form (/services/:id/monitors/new etc.)

Section titled “Create / Edit Form (/services/:id/monitors/new etc.)”
FieldRequiredNotes
TypeHTTP / TCP / Ping. Cannot be changed after creation
Display nameAuto-generated from the configuration when left blank (e.g. example.com /path)
Check interval3 / 5 / 10 / 30 min / 1 hour. Options shorter than your plan minimum are disabled (Free: 5 min+ / Pro: 3 min+)
FieldRequiredRange / default
URLPublic http(s):// URL (max 2048 chars)
MethodGET / HEAD / POST (default GET)
Expected status100–599 (default 200)
KeywordString check against the response body
Keyword condition“Must be present” (default) or must be absent
Timeout (ms)1000–30000 (default 10000)
FieldRequiredRange / default
HostnamePublic hostname
Port1–65535
Timeout (ms)1000–30000 (default 10000)
FieldRequiredRange / default
HostnamePublic hostname
Port1–65535 (default 443). Reachability is checked via TCP connect
Timeout (ms)1000–30000 (default 10000)

Monitor Detail (/services/:id/monitors/:mid)

Section titled “Monitor Detail (/services/:id/monitors/:mid)”
BadgeMeaning
Up (green)Healthy
Down (red)Outage detected
Degraded (yellow)Indeterminate. The current HTTP / TCP / Ping monitors only return up / down, so this state does not occur
Paused (gray)Checks stopped
Pending / initializing (blue)Waiting for the first check
Under maintenance (blue)Maintenance window active
  • Check now: runs an immediate check and shows the result inline. Rapid consecutive runs are limited (a 5-minute cooldown notice appears when exceeded)
  • Start / end maintenance
  • Reset statistics: resets uptime display, either “all time” or “before a chosen date”. Cannot be undone
  • Edit: opens the edit form (deletion is done from the service detail monitor list)
  • HTTP / TCP / Ping: response time chart for the last 50 checks, average response time, uptime. A “response time anomaly” badge appears when responses deviate strongly from the baseline

You can attach channels directly to a monitor. With no attached channels, team-wide channels are notified; attaching even one channel restricts notifications to the attached ones (see Notification Behavior).