Observability

ByteBite observability is application-level today. Centralized infrastructure monitoring is not yet deployed.

Health checks

Endpoint	Purpose	Tenant lookup
`GET /health`	Liveness — `{"status":"ok","service":"bytebite-api"}`	Skipped
`GET /health/db`	Database connectivity — `ok` or `degraded`	Skipped

Accessible on direct API hosts and same-origin /api/health through Traefik.

Defined in Dockerfiles (HEALTHCHECK directive):

Local dev additionally healthchecks PostgreSQL (pg_isready) and MinIO (mc ready).

Storefront depends_on: api: condition: service_healthy in compose.deploy.yml.

Aspect	Detail
Package	`packages/observability`
Configuration	`SENTRY_DSN` environment variable
Local dev	Optional — `initSentry` is a no-op without DSN
Staging	Configured via Dokploy (optional)
Production	Required when deployed (planned)

Never document DSN values.

Aspect	Detail
Library	pino (`packages/observability`)
Format	JSON in production, pretty-printed in development
Level	`LOG_LEVEL` env var (default `info` in staging compose)
Centralized aggregation	Not deployed

Capability	Status
Docker container status	Available via `docker ps` / Dokploy UI
Traefik access/error logs	Container logs on APP VM
Dokploy deployment logs	Dokploy UI
Centralized logging (Loki, ELK, etc.)	Not deployed
Alerting / paging	Not deployed
Uptime monitoring (external)	Not deployed
Infrastructure metrics (Prometheus, etc.)	Not deployed
Backup monitoring	Not deployed

After infrastructure changes, run the Validation smoke test suite. For application-level health, see Operations overview.