Log statements that provide the ability to trace the progress and behavior involved in tracking a single activity.
Log statements that provide the ability to trace the progress and behavior involved in tracking a single activity. These are useful for debugging general issues, identifying how modules are interacting, etc.
The highest logging severity.
The highest logging severity. This generally indicates an application or system error that causes undesired outcomes. An error generally indicates a bug or an environment problem that warrants some kind of immediate intervention.
Indicates normal high-level activity.
Indicates normal high-level activity. Generally a single user– or system-initiated activity will trigger one or two info-level statements. (E.g., one when starting and one when finishing for complex requests.)
A singleton used for accessing the mapped diagnostic context of your loggers.
A singleton used for accessing the mapped diagnostic context of your loggers. This acts like a regular map, except that the values are different in every thread.
Getting and setting single values and clearing the map are fast operations operations, but other operations, including getting the size, requires making a copy of the MDC.
Highly localized log statements useful for tracking the decisions made inside a single unit of code.
Highly localized log statements useful for tracking the decisions made inside a single unit of code. These may occur at a very high frequency.
Generally indicates something is not expected but the system is able to continue operating.
Generally indicates something is not expected but the system is able to continue operating. This generally indicates a bug or environment problem that does not require urgent intervention.