Getting started
Create your first monitor
What a monitor is, what to point it at, and how often it should run.
A monitor is a single recurring check against one target — usually a URL. When you create one you decide three things.
What to monitor
Start with a page whose failure costs you something: your home page, your sign-up flow, or an API health endpoint. One monitor per distinct thing you care about keeps results easy to read.
How often to check
Shorter intervals catch problems sooner but produce more data. A one to five minute interval suits most public pages.
What counts as healthy
Decide what a passing check looks like — typically a 2x status code and a
response received inside a time budget you set.