Documentation

Documentation

PageLantern documentation.

Guides for every monitor type, every alert channel, the REST API, and the operational states you will see in the product — plus a plain-language glossary.

Start here

Monitor types

Website monitoring guide

HTTP uptime checks: status codes, content assertions, latency, and how PageLantern identifies itself.

API monitoring guide

Single and multi-step API checks with JSONPath assertions, variable extraction, and HAR export.

Heartbeat monitoring guide

Dead-man’s-switch monitoring for cron jobs and background workers: ping a URL, get alerted when the ping stops.

DNS and TCP monitoring

Verify that records resolve to the values you expect and that public ports are reachable — so routing failures are not mistaken for application failures.

Browser checks

Run a real browser against the flows that matter — login, checkout, search — and keep screenshots, traces and console output as evidence when they break.

Alerting and incidents

Alerts and notification channels

Set up every alert channel PageLantern supports, route alerts per monitor, and tune thresholds so the alerts you get are the ones you act on.

Sharing status

Status pages guide

Hosted public status pages: publishing incidents, maintenance windows, and subscriber updates.

Customising a status page

Components, branding, maintenance windows and subscribers — everything beyond publishing the page itself.

Platform

API keys

Create, scope, rotate and revoke the keys that authenticate programmatic access.

Reference

API reference

Authentication, conventions, rate limits, and the endpoints for monitors, incidents, status pages and results.

Monitoring glossary

Plain definitions of uptime monitoring, synthetic monitoring, status pages, heartbeats, SSL expiry, SLA/SLO, error budgets, and related terms.