Create your first monitor
A monitor is an HTTP check or an SSL certificate check that runs on a schedule from the regions you choose. This page walks through creating one.
- Navigate to
/dashboard/monitors/new. This opens the new monitor form.
- Choose a monitor type and give it a Name. Select HTTP monitor to check that a URL returns the status code you expect, SSL certificate check to watch a certificate's expiry date, or Domain expiry check to watch when a domain's registration runs out. SSL and domain expiry warnings are off until you set the number of days (see SSL monitoring and Domain expiry monitoring).
- Fill in the type-specific fields. For an HTTP monitor, enter the URL to check, choose a Method (GET, POST, PUT, DELETE, or HEAD), and set the Expected status code. For an SSL certificate check, enter the Hostname and the Port (defaults to 443). To be warned before the certificate expires, set Warn before expiry (days); leave it empty and no warning is sent. For a domain expiry check, enter the registered Domain (for example
example.com) and, to be warned, Warn before expiry (days). Domain expiry checks work only for TLDs whose registry publishes an RDAP service; others, such as .io, .co, .me and .de, are rejected when you save. A domain expiry check has no interval, timeout or regions, so skip the next step for it.
- Set the check interval, timeout, and regions. Check interval options are 1 min, 3 min, 5 min, 15 min, 30 min, and 1 hour — 5 min is the default, and options below your plan's minimum (3 min on Free) are disabled. Timeout controls how long a check waits before failing. Regions are US East, EU West, and Asia; US East is selected by default.
- Check the notification policy. The Notification policy field decides which alert channels are notified when this monitor's status changes. It's preselected to your team's
Default policy, which shows Default (no channels) until you add a channel in the next section. Keep it: a monitor set to None (no alerts) alerts no one, even after you add channels.
- Click Create monitor. Your monitor is saved and scheduling begins.
#What happens next
Stector starts running checks on the interval and regions you chose. Results appear on the monitor's detail page in the dashboard. If the monitor goes down, an incident is opened automatically (see Monitoring HTTP endpoints for when that happens, and Maintenance windows for the exception).
#What's next
Continue to Set up alert channels to get notified when a monitor's status changes.