Skip to content
DedNets Docsv0.5.0

Monitor a URL or endpoint with an uptime check

An uptime monitor actively probes a target on a schedule and records whether it answered. Use it to check that a website, API or TCP service is up. It is the mirror image of a watchdog: a watchdog waits to be pinged by a job, while an uptime monitor reaches out and checks. (Monitors since v0.4.5; daemon-origin probing, the Console page and the MCP tools since v0.5.0.)

Create a monitor

Section titled “Create a monitor”

Open Uptime in the Console (under Applications) and choose New monitor.

  • Name - a short identifier (letters, digits, hyphens, underscores).
  • Probe from - where the check runs:
    • DedNets edge probes from our edge over verified TLS. It can only reach public targets: private, loopback and link-local addresses are refused.
    • One of your daemons probes from a host you own, so it can reach anything that host can - including private services inside your network.
  • Type - HTTP to probe a URL, or TCP to open a host:port.
  • Target - the URL (https://example.com/health) for HTTP, or host:port (db.example.com:5432) for TCP.
  • Interval - how often to probe, between 30 seconds and 1 hour.

For an HTTP monitor you can also require:

  • Status codes - which HTTP codes count as up, e.g. 200 or 200-299,301. Leave it empty to accept any response the server returns.
  • Header checks - up to five assertions on the response headers, each a header name plus an operator (exists, equals or contains) and, for the last two, a value. Values are compared case-insensitively.

Read the results

Section titled “Read the results”

Each monitor shows a live state and a 24-hour uptime strip:

  • up - the last probe succeeded.
  • down - the last probe failed a check or could not connect. The row shows the exact reason (for example HTTP 503 Service Unavailable (want 200-299) or a header that did not match).
  • unknown - no probe has completed yet, or the target could not be probed.
  • offline - the daemon running a daemon-origin probe is offline.

Open a monitor for the window tabs (hour / day / week), the availability strip, and the last-check detail. A daemon-origin monitor’s current state is read from its availability history rather than the row badge.

When a monitor goes down, DedNets alerts your account through the uptime notification topic (the same delivery as watchdogs and service health). Pause a monitor for planned maintenance to suppress probing and alerts without losing its history.

Drive it from an agent or the API

Section titled “Drive it from an agent or the API”

The same monitors are available to an AI agent over MCP (uptime_create, uptime_list, uptime_update, uptime_pause, uptime_resume, uptime_delete, and uptime_status to troubleshoot) and over the automation API. See Let an AI agent run DedNets and Script the API. Both need an API token with the uptime:manage scope (the reads also accept read).

See also

Section titled “See also”