| Metadata |
Timestamp, file, line, information |
Locate
Where and when did it happen with what information?
|
P1
|
| Levels & Diagnostics |
Log levels, stack traces |
Filter
How severe is it, what evidence do we have?
|
P1
|
| Dispatch & Sinks |
Multiple sinks (console, file, remote) |
Reach
Who sees summaries, who keeps full logs?
|
P1
|
| Logging Architecture |
Global logger (singleton), config at entrypoint |
Unify
Is logging configuration consistent across the project?
|
P1
|
| Storage Strategy |
File rotation and retention |
Survive
Will the disk explode, how long do we keep logs?
|
P2
|
| Cloud Compatibility |
Structured logs (JSON) |
Query
Can log platforms search, visualize, analyze data out of box?
|
P2
|
| Performance Mechanism |
Async logging, enqueue and background flush |
Cost
Does logging slow down the business path?
|
P2
|
| Environment Awareness |
Config files/centers with environment overrides |
Tune
Adjust log levels and sinks per module and env at runtime.
|
P2
|
| Security Compliance |
Data masking, sensitive information redaction |
Privacy
Is there sensitive data in plain text logs?
|
P3
|
| Context Tracing |
Context-bound logs, request and trace IDs |
Correlate
How to tie all logs of one request together?
|
P3
|
| Sampling & Limiting |
Log sampling, deduplication, rate limiting |
Protect
Can the service stay healthy under log storms while keeping key logs?
|
P3
|
| Resilience Strategy |
No fatal on write errors, degraded mode, fallbacks |
Robustness
Can the logger fail harmlessly, and expose its degraded state?
|
P3
|