Observability
Logging Architecture
Structured logging with centralized aggregation, powerful search, and intelligent alerting.
2.4TB
Log Volume
Per day
90d
Retention
Hot storage
< 2s
Search Latency
P95
47
Alert Rules
Active
Logging Strategy
Structured JSON logs with consistent schemas across services.
# Logging Strategy ## Log Levels ├── DEBUG - Detailed diagnostic info ├── INFO - Normal operations ├── WARNING - Unexpected but handled ├── ERROR - Operation failed └── CRITICAL - System failure ## When to Log ### INFO Level - Request received/completed - Background job started/finished - Cache hits/misses - External API calls ### WARNING Level - Retry attempts - Degraded performance - Approaching rate limits - Deprecated API usage ### ERROR Level - Request failures - External service errors - Database errors - Validation failures ### DEBUG Level (dev/staging only) - SQL queries - Request/response bodies - Cache operations - Feature flag evaluations ## What NOT to Log ✗ Passwords, API keys, tokens ✗ Full credit card numbers ✗ PII without redaction ✗ Session cookies
Log Policies
Structured FormatRequired
All logs must be JSON with required fields
Request CorrelationRequired
Include trace_id, span_id on every log
PII RedactionAutomated
Automatically redact sensitive fields
Rate LimitingEnforced
Max 1000 logs/sec per service
Retention TiersAutomated
Hot: 90d, Warm: 1y, Cold: 7y
Complete Visibility
Structured logging enables fast debugging and proactive monitoring.
2.4 TB/day<2s Search90d Retention