Quickstart
Go from zero to your first monitor and alert in under 10 minutes.
Before you begin
You need a browser and an email address. No credit card is required for the Free plan.
Step 1: Create your workspace
- Go to
/signupand enter your email address. - Choose a workspace name (e.g.
acme-ops) — a unique display name for your team. It has no effect on any public URL; see Sign up for how status page URLs are actually generated. - Verify your email: check your inbox for the confirmation link.
- Log in. You land on the Dashboard.
Step 2: Add your first HTTP monitor
- In the sidebar, click Monitors.
- Click + New Monitor and choose HTTP / HTTPS.
- Fill in the two required fields:
| Field | Example value |
|---|---|
| Name | Production API |
| URL | https://api.example.com/health |
- Leave everything else at its default (120s check interval, 2xx expected status) and click Save. See First monitor for the full field reference, including keyword checks, SSL monitoring, and alert thresholds.
The monitor runs its first check within seconds. The status indicator turns green once the first successful check returns.
Step 3: Add a notification channel
Without a notification channel, incidents are created but you will not receive alerts.
- In the sidebar, click Integrations.
- Click + Add Channel and choose Email.
- Enter the email address where you want to receive alerts.
- Click Save, then click Send Test Alert to verify delivery.
Step 4: Attach the channel to your monitor
- Go back to Monitors and open the monitor you created.
- Click Edit.
- In the Notifications section, select the email channel from the dropdown.
- Click Save.
Your monitor now triggers an alert to your email when the endpoint goes down.
What happens next
- The monitor checks your URL every 120 seconds from a HowlOps prober node.
- If the check fails, an incident is created and an alert is sent.
- When the endpoint recovers, the incident resolves automatically and a recovery email is sent.
Continue to Sign up for workspace settings, or jump to Concepts to understand how monitors, heartbeats, and incidents fit together.
Was this page helpful?