Staging Deployment
Logging Guide
Sprint 23 adds a structured logging helper for staging diagnostics. Log entries are JSON lines with:
Use this when you need detailed reference information for Staging Deployment.
Sprint 23 adds a structured logging helper for staging diagnostics. Log entries are JSON lines with:
- level
- message
- timestamp
- app
- environment
- request id when available
- safe contextual metadata
LOG_LEVEL controls verbosity and accepts debug, info, warn, or error. Local development can use debug; staging should normally use info.
Sensitive keys such as password, secret, token, API key, authorization, cookie, and database connection values are redacted before logging.
Use the x-request-id response header from /api/health and /api/ready to correlate browser checks with server logs.
Developer Details
- Source
- apps/docs/content/staging-deployment/logging.md
- Owner
- Platform / Operations
- Status
- Current
- Module
- Staging Deployment
- Related route
- /api/health