Monitor Next.js

Why monitor Next.js

Setting up Next.js monitoring

1. 1
   Expose an /api/health endpoint that returns 200 when dependencies (DB, cache, auth) respond. Use the App Router route handler above or a Pages-Router equivalent.
2. 2
   Route handlers are dynamic by default in Next.js 15+; keep `export const dynamic = "force-dynamic"` as a safety net so a future opt-in to caching cannot freeze a stale "ok" response.
3. 3
   Add https://yourapp.com/api/health in Hyperping → New monitor → HTTP, interval 30s.
4. 4
   Turn on keyword matching for "ok" to catch routes that 200 with an empty body during build failures.
5. 5
   Add a second SSL monitor on the apex domain. Vercel auto-renews, but custom edge configs can stall.
6. 6
   Wire alerts to Slack/PagerDuty with a 2-minute confirmation window to absorb Vercel deploy blips.

Example health endpoint

import { NextResponse } from 'next/server';

// Route handlers are dynamic by default in Next.js 15+.
// force-dynamic is defensive so a future opt-in to caching cannot freeze a stale response.
export const dynamic = 'force-dynamic';

export async function GET() {
  const checks = {
    db: await pingDatabase(),
    redis: await pingRedis(),
  };

  const healthy = Object.values(checks).every(Boolean);

  return NextResponse.json(
    { status: healthy ? 'ok' : 'degraded', checks, ts: Date.now() },
    { status: healthy ? 200 : 503 }
  );
}

What typically goes wrong with Next.js

Frequently asked questions