DIDO Wiki

return to the Apache Foundation

Note: The following is an excerpt from the official Apache Log4net site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference.

Source: What is Apache Log4net : The Apache log4net library is a tool to help the programmer output log statements to a variety of output targets. log4net is a port of the excellent Apache log4j™ framework to the Microsoft® .NET runtime. We have kept the framework similar in spirit to the original log4j while taking advantage of new features in the .NET runtime. For more information on log4net see the features document.

Source: Introduction Manual

• Writes logging events to a database using either prepared statements or stored procedures.
• Writes color highlighted logging events to a an ANSI terminal window.
• Writes logging events to the ASP trace context. These can then be rendered at the end of the ASP page or on the ASP trace page.
• Buffers logging events before forwarding them to child appenders.
• Writes logging events to the application's Console. The events may go to either the standard our stream or the standard error stream. The events may have configurable text and background colors defined for each level.
• Writes logging events to the application's Console. The events may go to either the standard our stream or the standard error stream.
• Writes logging events to the .NET system.
• Writes logging events to the Windows Event Log.
• Writes logging events to a file in the file system.
• Forwards logging events to child appenders.
• Writes logging events to the local SYSLOG service (UNIX only).
• Stores logging events in an in memory buffer.
• Writes logging events to the Windows Messenger service. These messages are displayed in a dialog on a users terminal.
• Writes logging events to the debugger. If the application has no debugger, the system debugger displays the string. If the application has no debugger and the system debugger is not active, the message is ignored.
• Writes logging events to a remote SYSLOG service service using UDP networking.
• Writes logging events to a remoting sink using .NET remoting.
• Writes logging events to a file in the file system. The RollingFileAppender can be configured to log to multiple files based upon date or file size constraints.
• Sends logging events to an email address.
• Writes SMTP messages as files into a pickup directory. These files can then be read and sent by an SMTP agent such as the IIS SMTP agent.
• Clients connect via Telnet to receive logging events.
• Writes logging events to the .NET trace system.
• Sends logging events as connectionless UDP datagrams to a remote host or a multicast group using a UdpClient.