What niceuptime monitors

Getting StartedUpdated Jul 16, 20262 min read

niceuptime has two monitor types.

A Pulse is for work you run yourself, such as a cron job or backup. Your job reports a Heartbeat to its tokenized endpoint after the work succeeds.

A Probe is an outbound GET or HEAD check run by niceuptime against a public HTTP or HTTPS URL. Its results are recorded as Heartbeats for the monitors that use that target.

From evidence to state

A Heartbeat is one observation of success or failure. niceuptime evaluates those observations against the monitor policy to derive its current state.

When that state becomes failing, an Incident can open. When later successful Heartbeats satisfy recovery policy, the Incident can resolve.

Start with the monitor type that matches where the work happens: Pulse when your job can report in, or Probe when niceuptime should make the HTTP request.

Create your first monitor

Pick a Pulse or Probe, enter the required details, and save to begin collecting evidence.

3 min read

Create your first HTTP probe

Configure a public GET or HEAD target, its expected status, interval, and allowed regions.

3 min read