Docs/Lighthouse
Lighthouse
Lighthouse is the Status Harbor agent for monitoring services that the public internet can't reach: internal APIs, private databases, k8s services behind an Ingress, anything inside a VPC, on-prem or behind a firewall.
You run the agent inside your network. It dials out to Status Harbor over HTTPS, registers with a scoped token, then runs the monitors you've bound to it from inside the network. No inbound exposure, no VPN peering.
What it monitors
- HTTP / HTTPS — same as public, including expected status, keyword match, headers, basic auth.
- TCP — connect succeeds.
- UDP — send a payload, expect a response.
SSL and DNS monitors run from public probes only — they don't provide value behind a firewall.
How it differs from public monitors
| Public | Lighthouse | |
|---|---|---|
| Where checks run | Status Harbor regional probes | Your agent |
| Min interval | Plan-dependent (5–60s) | 5s, hard floor |
| Regions | One or more selectable | The agent's location |
| Flap protection | Single-fail opens, single-pass resolves | Configurable consecutive-result threshold |
Pieces
- Install — Shell, Docker, Helm or Terraform.
- Discovery — auto-find Kubernetes Ingresses and Services and adopt them as monitors.
- Troubleshooting — what to check when the agent is offline.
Limits
Both Free and Pro include Lighthouse agents. Current per-plan caps are listed on the pricing page; see Plans & limits for the full capability matrix.