Class ScriptAppenderSelector
java.lang.Object
org.apache.logging.log4j.core.AbstractLifeCycle
org.apache.logging.log4j.core.filter.AbstractFilterable
org.apache.logging.log4j.core.appender.AbstractAppender
org.apache.logging.log4j.core.appender.ScriptAppenderSelector
- All Implemented Interfaces:
Appender, Filterable, LocationAware, LifeCycle, LifeCycle2
@Plugin(name="ScriptAppenderSelector",
category="Core",
elementType="appender",
printObject=true)
public class ScriptAppenderSelector
extends AbstractAppender
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic final classBuilds an appender.Nested classes/interfaces inherited from interface LifeCycle
LifeCycle.State -
Field Summary
Fields inherited from class AbstractLifeCycle
DEFAULT_STOP_TIMEOUT, DEFAULT_STOP_TIMEUNIT, LOGGERFields inherited from interface Appender
ELEMENT_TYPE, EMPTY_ARRAY -
Constructor Summary
ConstructorsModifierConstructorDescriptionprivateScriptAppenderSelector(String name, Filter filter, Layout<? extends Serializable> layout, Property[] properties) -
Method Summary
Modifier and TypeMethodDescriptionvoidLogs a LogEvent using whatever logic this Appender wishes to use.Methods inherited from class AbstractAppender
error, error, error, getHandler, getLayout, getName, ignoreExceptions, parseInt, requiresLocation, setHandler, toSerializable, toStringMethods inherited from class AbstractFilterable
addFilter, getFilter, getPropertyArray, hasFilter, isFiltered, removeFilter, start, stop, stopMethods inherited from class AbstractLifeCycle
equalsImpl, getState, getStatusLogger, hashCodeImpl, initialize, isInitialized, isStarted, isStarting, isStopped, isStopping, setStarted, setStarting, setState, setStopped, setStopping, stop, stop
-
Constructor Details
-
ScriptAppenderSelector
private ScriptAppenderSelector(String name, Filter filter, Layout<? extends Serializable> layout, Property[] properties)
-
-
Method Details
-
newBuilder
-
append
Description copied from interface:AppenderLogs a LogEvent using whatever logic this Appender wishes to use. It is typically recommended to use a bridge pattern not only for the benefits from decoupling an Appender from its implementation, but it is also handy for sharing resources which may require some form of locking.- Parameters:
event- The LogEvent.
-