Severity Hierarchy
When to Use Each Level
debug
Use for information only needed during active debugging. These logs are typically high-volume and disabled in production:- Database query details and timing
- Cache hit/miss events
- Internal function entry/exit
- Configuration values at startup
info
Use for events that confirm the system is working correctly. These form the baseline of operational visibility:- User actions (sign-in, sign-out, purchase)
- Job or request completion
- Service startup and shutdown
- Scheduled task execution
warn
Use when something unexpected happens but the system can continue. Warnings often indicate future problems:- Rate limits nearing capacity
- Fallback behavior triggered
- Deprecated feature usage
- Slow operations exceeding thresholds
error
Use for failures that need attention. Errors mean something went wrong and likely needs a fix:- Unhandled exceptions
- External service failures
- Data validation errors in critical paths
- Resource exhaustion (disk, memory, connections)
Level Filtering
You can set a minimum log level to control which logs are sent. WhenminLevel is set, only logs at that level or higher are transmitted:
This is useful for reducing noise in production while keeping full verbosity in development.
Dashboard Colors
In the Timberlogs dashboard, each level is color-coded for quick visual scanning:Further Reading
- Structured Logging — how structured data makes logs searchable
- SDK Logging Methods: TypeScript | Python — sending logs with different levels
- Viewing Logs — filtering and searching logs in the dashboard