log4net

Appender that logs to a database.

appends logging events to a table within a database. The appender can be configured to specify the connection string by setting the property. The connection type (provider) can be specified by setting the property. For more information on database connection strings for your specific database see http://www.connectionstrings.com/. Records are written into the database either using a prepared statement or a stored procedure. The property is set to (System.Data.CommandType.Text) to specify a prepared statement or to (System.Data.CommandType.StoredProcedure) to specify a stored procedure. The prepared statement text or the name of the stored procedure must be set in the property. The prepared statement or stored procedure can take a number of parameters. Parameters are added using the method. This adds a single to the ordered list of parameters. The type may be subclassed if required to provide database specific functionality. The specifies the parameter name, database type, size, and how the value should be generated using a . An example of a SQL Server table that could be logged to:


            CREATE TABLE [dbo].[Log] ( 
              [ID] [int] IDENTITY (1, 1) NOT NULL ,
              [Date] [datetime] NOT NULL ,
              [Thread] [varchar] (255) NOT NULL ,
              [Level] [varchar] (20) NOT NULL ,
              [Logger] [varchar] (255) NOT NULL ,
              [Message] [varchar] (4000) NOT NULL 
            ) ON [PRIMARY]

An example configuration to log to the above table:

Julian Biddle Nicko Cadell Gert Driesen Lance Nehring

Abstract base class implementation of that buffers events in a fixed size buffer.

This base class should be used by appenders that need to buffer a number of events before logging them. For example the buffers events and then submits the entire contents of the buffer to the underlying database in one go. Subclasses should override the method to deliver the buffered events. The BufferingAppenderSkeleton maintains a fixed size cyclic buffer of events. The size of the buffer is set using the property. A is used to inspect each event as it arrives in the appender. If the triggers, then the current buffer is sent immediately (see ). Otherwise the event is stored in the buffer. For example, an evaluator can be used to deliver the events immediately when an ERROR event arrives. The buffering appender can be configured in a mode. By default the appender is NOT lossy. When the buffer is full all the buffered events are sent with . If the property is set to true then the buffer will not be sent when it is full, and new events arriving in the appender will overwrite the oldest event in the buffer. In lossy mode the buffer will only be sent when the triggers. This can be useful behavior when you need to know about ERROR events but not about events with a lower level, configure an evaluator that will trigger when an ERROR event arrives, the whole buffer will be sent which gives a history of events leading up to the ERROR event. Nicko Cadell Gert Driesen

Abstract base class implementation of .

This class provides the code for common functionality, such as support for threshold filtering and support for general filters. Appenders can also implement the interface. Therefore they would require that the method be called after the appenders properties have been configured. Nicko Cadell Gert Driesen

Implement this interface for your own strategies for printing log statements.

Implementors should consider extending the class which provides a default implementation of this interface. Appenders can also implement the interface. Therefore they would require that the method be called after the appenders properties have been configured. Nicko Cadell Gert Driesen

Closes the appender and releases resources.

Releases any resources allocated within the appender such as file handles, network connections, etc. It is a programming error to append to a closed appender.

Log the logging event in Appender specific way.

The event to log This method is called to log a message into this appender.

Gets or sets the name of this appender.

The name of the appender. The name uniquely identifies the appender.

Interface for appenders that support bulk logging.

This interface extends the interface to support bulk logging of objects. Appenders should only implement this interface if they can bulk log efficiently. Nicko Cadell

Log the array of logging events in Appender specific way.

The events to log This method is called to log an array of events into this appender.

Interface used to delay activate a configured object.

This allows an object to defer activation of its options until all options have been set. This is required for components which have related options that remain ambiguous until all are set. If a component implements this interface then the method must be called by the container after its all the configured properties have been set and before the component can be used. Nicko Cadell

Activate the options that were previously set with calls to properties.

This allows an object to defer activation of its options until all options have been set. This is required for components which have related options that remain ambiguous until all are set. If a component implements this interface then this method must be called after its properties have been set before the component can be used.

Interface that can be implemented by Appenders that buffer logging data and expose a method.

Flushes any buffered log data.

Appenders that implement the method must do so in a thread-safe manner: it can be called concurrently with the method. Typically this is done by locking on the Appender instance, e.g.:

The parameter is only relevant for appenders that process logging events asynchronously, such as . The maximum time to wait for logging events to be flushed. True if all logging events were flushed successfully, else false.

Initial buffer size

Maximum buffer size before it is recycled

Default constructor

Empty default constructor