HowlOps docs

How can we help you ship reliable monitoring?

Everything about setting up checks, routing alerts to the right person, and telling your users what is going on.

Browse by section

Welcome: what do you need to do?

Choose the outcome closest to your task. You will get three ordered links instead of having to understand the documentation structure first.

One product flow

The same alert path is used across the product and these docs. Select a source to see which details change and which steps stay the same.

INTERACTIVE PRODUCT TOUR

See what happens after a signal arrives.

Choose a source. The first checks change, but routing, paging, response, and recovery stay connected.

01

Signal

A probe reports that the configured target failed.

02

Confirm

Retries, thresholds, and optional regional rules confirm the condition before opening an alert.

03

Route

Routing rules select a policy; without one, enabled channels receive the alert.

04

Reach

The policy pages its current target and continues only while the alert is unacknowledged.

05

Respond

Acknowledge, coordinate, and publish updates. Recovery resolves the alert and sends the all-clear.

Alerts notify immediately. Promotion to a tracked incident is automatic by rule or manual. Read the alert flow

API in one minute

bash
curl -H "Authorization: Bearer $HOWLOPS_TOKEN" \
     https://api.howlops.com/api/v1/monitors

Use the REST API reference for authentication, request shapes, pagination, and errors. Product changes are listed in What's new.

Recently updated

Was this page helpful?