| Interface | Description |
|---|---|
| LogBuilder |
Interface for constructing log events before logging them.
|
| Logger |
This is the central interface in the log4j package.
|
| Marker |
Markers are objects that are used to add easily filterable information to log messages.
|
| ThreadContext.ContextStack |
The ThreadContext Stack interface.
|
| Class | Description |
|---|---|
| CloseableThreadContext |
Adds entries to the
stack or map and them removes them when the object is closed, e.g. |
| CloseableThreadContext.Instance | |
| EventLogger |
Logs "Events" that are represented as
StructuredDataMessage. |
| Level |
Levels used for identifying the severity of an event.
|
| LogManager |
The anchor point for the Log4j logging system.
|
| MarkerManager |
Applications create Markers by using the Marker Manager.
|
| MarkerManager.Log4jMarker |
Consider this class private, it is only public to satisfy Jackson for XML and JSON IO.
|
| ThreadContext |
The ThreadContext allows applications to store information either in a Map or a Stack.
|
| Exception | Description |
|---|---|
| LoggingException |
Exception thrown when an error occurs while logging.
|
The main entry point into Log4j is the LogManager class which can be used to
obtain Logger objects, the current
LoggerContext, a new LoggerContext, and the current
LoggerContextFactory.
Marker objects can be obtained through the
MarkerManager. The MDC (Mapped Diagnostic Context) can be
used through the ThreadContext class.
Copyright © 2021 JBoss by Red Hat. All rights reserved.