Log Level Converter & Severity Mapper
Instantly translate and correlate severity levels across different logging frameworks, system facilities, and standard protocols like RFC 5424.
| Framework / Standard | Equivalent Level Name | Numeric Severity / Code |
|---|
Framework Severity Reference Matrix
Comprehensive breakdown of integer values and severity mappings used across common backend and enterprise platforms.
| Severity Tier | Syslog (RFC 5424) | .NET / MEL | Log4j / SLF4J | Python |
|---|---|---|---|---|
| Emergency / Critical | 0 - Emergency |
Critical (6) | FATAL / OFF | CRITICAL (50) |
| Error / Alert | 3 - Error |
Error (4) | ERROR | ERROR (40) |
| Warning | 4 - Warning |
Warning (3) | WARN | WARNING (30) |
| Informational | 6 - Informational |
Information (2) | INFO | INFO (20) |
| Debug / Trace | 7 - Debug |
Debug (1) / Trace (0) | DEBUG / TRACE | DEBUG (10) / NOTSET (0) |
Frequently Asked Questions (FAQ)
Unix Syslog protocols traditionally use lower numbers for higher severity (e.g., 0 for Emergency), whereas modern application frameworks like Python, .NET, and Log4j assign higher integers to more critical logs to allow threshold filtering (e.g., setting a minimum logging level threshold).
Most cloud aggregators (such as OpenTelemetry, Datadog, or AWS CloudWatch) rely on Syslog severity standards or OpenTelemetry SeverityNumber specifications to normalize cross-platform microservice logs into unified dashboards.