FaultPilot
FaultPilot home

FaultPilot documentation

Uptime monitors

Configure public checks, confirmation thresholds, timeouts, maintenance, and reliable alert delivery.

Open in FaultPilot
1

Choose the correct check

  1. Use HTTP or website monitoring for public web endpoints.
  2. Use SSL and domain-expiration checks for certificate and registration lifecycle visibility.
  3. Monitor a lightweight readiness endpoint when possible instead of a slow business transaction.
2

Configure reliability

  1. Set a timeout that reflects the endpoint's normal worst-case response time.
  2. Use consecutive failure and recovery thresholds to avoid alerts from one transient result.
  3. Treat expected authentication responses explicitly; avoid repeatedly testing a throttled login endpoint.
  4. FaultPilot suppresses customer-down alerts when its runner or outbound network cannot provide trustworthy evidence.
3

Connect operations

  1. Attach active email, Slack, or webhook destinations.
  2. Connect customer-visible monitors to a status page.
  3. Add planned work to a maintenance window before checks begin failing.
4

Interpret state

  1. UP means the latest confirmed state is healthy.
  2. DOWN requires the configured number of consecutive counted failures.
  3. UNKNOWN means FaultPilot cannot currently produce trustworthy evidence and should not blame the customer target.
  4. DEGRADED is reserved for partial or policy-defined impairment, not one arbitrary failed check.