Skip to content
WireWatch Docs

WireWatch documentation

WireWatch checks that your sites, services and APIs are up and answering correctly. A monitor probes a target on a fixed interval from WireWatch regions or from an agent inside your own network; when the locations probing it agree the target is down, WireWatch opens an incident, alerts the channels you chose, and can show the outage on a public status page. The product is at app.wirewatch.io.

New here? Getting started takes you from sign-up to your first alert, inside the Free plan.

Monitors

Section titled “Monitors”
  • Monitor types — the seven types, what each probes and what it stores.
  • Check intervals — how often a monitor can be probed, and what decides it.
  • Probe locations — WireWatch regions, your own agents, and the quorum over them.
  • Assertions — what an http monitor can check in a response, and which assertions are evaluated today.
  • Services — grouping monitors, and the status a group derives.

Agents

Section titled “Agents”

Notifications

Section titled “Notifications”
  • Notifications — channels and the three events that trigger a send.
  • Channels — the five channel types and their fields.
  • Policies — which policy an incident uses, and what it contains.
  • Suppression — every reason an alert you expected did not arrive.
  • Webhooks and Payload — the body, the headers, and how to verify the signature.

Incidents

Section titled “Incidents”
  • Incidents — the states an incident moves through, severity, and the timeline.
  • Maintenance windows — keeping a planned outage from paging the team.

Status pages

Section titled “Status pages”

Our own is at status.wirewatch.io.

API reference

Section titled “API reference”