Start with a public health endpoint
Point an HTTP monitor at a publicly reachable endpoint such as /api/health. Track the expected response status without building a separate monitoring dashboard for every service.
Follow the availability and latency of public HTTP API endpoints, with incident and recovery history when responses stop behaving as expected.
{
"status": "ok"
}Fictional sequence. Animation timing is not check cadence or a performance promise.
Point an HTTP monitor at a publicly reachable endpoint such as /api/health. Track the expected response status without building a separate monitoring dashboard for every service.
A successful response and a fast response are different observations. Compare response times over your selected period and review incidents around a deployment or dependency failure.
This is public HTTP endpoint monitoring. It is not an authenticated API test suite, request-script runner, or a promise of POST, PUT or GraphQL testing. Keep private endpoints and credentials out of monitor URLs.
In practice
These monitors are intended for publicly reachable HTTP endpoints. Do not add internal network targets or credentials to URLs.
Recovery is recorded in the incident history and can trigger a recovery email when notifications are enabled.
Connect the context
Review uptime, response time, MTBF and MTTR.
02Follow downtime, recovery and email notifications.
03Monitor availability, response time and downtime.
Start monitoring
Add your first monitor and keep website availability, performance and incident history in one clear place.
7-day Starter trial · No credit card required · Starts with your first monitor