Logs & Debugging

ScanPick logs to stdout. In production, redirect logs to a file or use your infrastructure’s log collection system.

Runtime Logs

Single Binary

./ScanPick.Api > scanpick.log 2>&1

The log file captures all API activity including startup, database migrations, requests, and errors.

Docker Compose

# All services
docker compose logs

# API only
docker compose logs api

# Follow (stream) API logs
docker compose logs -f api

Filtering Logs

# Errors only
docker compose logs api | grep -i error

# Specific worker activity
docker compose logs api | grep "worker-003"

# Database queries
docker compose logs api | grep "Executing DbCommand"

Development Mode

Set ASPNETCORE_ENVIRONMENT=Development for:

• Detailed error pages with stack traces
• Scalar API explorer at /scalar/v1
• More verbose logging
• EF Core SQL query logging

export ASPNETCORE_ENVIRONMENT=Development
./ScanPick.Api

Log Levels

Level	When to Use
Error	Production monitoring — unexpected failures
Warning	Production — non-critical issues
Information	Default — normal operational events
Debug	Troubleshooting — detailed flow information
Trace	Development — very detailed diagnostics

Log level is controlled via ASP.NET Core’s logging configuration. The default level is Information.

Common Log Messages

Message	Meaning
Applying migrations...	EF Core is updating the database schema
Seeding demo data...	First-run data initialization
License validated: {status}	License check result
PickTask {id} updated: {quantity}	Scan processed successfully
WebSocket connected: {id}	SignalR client connected
Health check: OK	API and database are operational