Next.js logging best practices
Production-ready logging patterns for Next.js apps on LoggerMan.
One token per deployable
Map each Vercel project (or environment) to a LoggerMan project. Use environment on createLogger instead of cloning projects for staging.
Log at HTTP boundaries
- Request start: method, path, requestId
- Success: status, durationMs
- Failure: ERROR with stable error code in metadata
See the Next.js API template for a starter snippet.
Avoid logging secrets
Never pass Authorization headers, cookies, or PII in metadata. LoggerMan sanitizes common patterns, but design messages assuming logs may be exported.
Middleware and edge
Use the edge export for middleware — keep payloads small and batch when possible. See Integrations for edge setup.
Alerts after volume
Once traffic is real, add a threshold or spike rule on ERROR. Read Alert fatigue before paging the whole team.