serverpod-health-checks

name	serverpod-health-checks
description	Serverpod health endpoints — /livez, /readyz, /startupz, custom HealthIndicator, HealthConfig. Use when configuring Kubernetes probes or monitoring server health.

Serverpod Health Checks

Kubernetes-style HTTP health endpoints. Unauthenticated: HTTP status only (200/503). Authenticated: detailed JSON (RFC Health Check Response Format).

Endpoints

• /livez — Process alive? Does not check DB/Redis. Use for liveness probes.
• /readyz — Dependencies healthy? Returns 503 if not. Use for readiness probes.
• /startupz — Server finished initializing? Use for startup probes.

Built-in indicators

• ServerpodStartupIndicator — startup complete
• DatabaseHealthIndicator — PostgreSQL (if configured)
• RedisHealthIndicator — Redis (if enabled)

Custom health indicator

class StripeApiIndicator extends HealthIndicator<double> {
  @override String get name => 'stripe:api';
  @override String get componentType => HealthComponentType.component.name;
  @override String get observedUnit => 'ms';
  @override Duration get timeout => const Duration(seconds: 3);

  @override
  Future<HealthCheckResult> check() async {
    final sw = Stopwatch()..start();
    try {
      await stripeClient.ping();
      return pass(observedValue: sw.elapsedMilliseconds.toDouble());
    } catch (e) {
      return fail(output: 'Stripe unavailable: $e');
    }
  }
}

Registration

final pod = Serverpod(args, Protocol(), Endpoints(),
  healthConfig: HealthConfig(
    cacheTtl: Duration(seconds: 2),
    additionalReadinessIndicators: [StripeApiIndicator()],
    additionalStartupIndicators: [CacheWarmupIndicator()],
  ),
);

Each indicator can override timeout (default 5s). cacheTtl caches results to reduce load under frequent probing.