liveBook · Manning

Severity

As explained in The Art of Code

A log severity level classifies the importance or urgency of a log record for filtering and routing.

Severity levels make logging selective rather than noisy: TRACE, DEBUG, INFO, WARN, and ERROR let deployments filter less important records while retaining useful operational signals. section 7.2.3

Choose an actionable error level

A parsing failure belongs at ERROR when it needs investigation, but the message should also identify the input and preserve the exception: logger.error("Invalid number format for input: {}", input, dataFormatException). section 7.2.3

How The Art of Code covers it

How deep it goes
Defines common levels and their filtering role, but does not detail a formal severity hierarchy or routing configuration.
Examples
Shows Java SLF4J ERROR statements for invalid numbers and date parsing, including contextual values and exceptions.
What you can do after
Apply severity via SLF4J logging statements that preserve useful errors while filtering less important records.
How it connects
Connects severity with logging libraries, filtering, monitoring, centralized logging, and exception handling.
Cover of The Art of Code
liveBookmanning.com
Read The Art of Code on liveBook Get the book at manning.com

Also explained in

Compare how 7 books explain severity →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of The Art of Code. The section links point to the parts of the book it draws on.