This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:apache:log4net [2020/05/05 20:49] nick ↷ Links adapted because of a move operation |
dido:public:ra:xapend:xapend.b_stds:defact:apache:log4net [2021/11/08 17:02] (current) nick ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======== Apache: log4net ========= | + | ===== Apache: log4net ===== |
| - | [[dido:public:apdx.stds:defact:apache| return to the Apache Foundation ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:apache:start| return to the Apache Foundation ]] |
| - | : **Note**: The following is an excerpt from the official Apache Log4j site. It is provided here as a connivence and is not authoritative. Refer to the original document as the authoritative reference. | + | : **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. |
| - | + | ||
| - | : // | + | |
| - | // | + | |
| <table> | <table> | ||
| Line 21: | Line 18: | ||
| </table> | </table> | ||
| - | + | ==== Introduction ==== | |
| - | + | ||
| - | ====== Introduction ====== | + | |
| Source: [[https://logging.apache.org/log4net/index.html | What is Apache Log4net ]] | Source: [[https://logging.apache.org/log4net/index.html | 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.// | : //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.// | ||
| - | ===== Features ===== | + | ==== Features ==== |
| - | Source: [[https://logging.apache.org/log4net/release/manual/introduction.html | Introduction Manual ]] | | + | Source: [[https://logging.apache.org/log4net/release/manual/introduction.html | Introduction Manual ]] |
| * Writes logging events to a database using either prepared statements or stored procedures. | * Writes logging events to a database using either prepared statements or stored procedures. | ||
| Line 40: | Line 35: | ||
| * Writes logging events to a file in the file system. | * Writes logging events to a file in the file system. | ||
| * Forwards logging events to child appenders. | * Forwards logging events to child appenders. | ||
| - | * Writes logging events to the local [[dido:public:apdx.stds:tech:ietf:syslog| SYSLOG service]] (**[[dido:public:glossary:u:unix]] only**). | + | * Writes logging events to the local [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:syslog| SYSLOG service]] (**[[dido:public:ra:xapend:xapend.a_glossary:u:unix]] only**). |
| * Stores logging events in an in memory buffer. | * 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 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 the debugger. If the [[dido:public:ra:xapend:xapend.a_glossary:a:application|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 [[dido:public:apdx.stds:tech:ietf:syslog| SYSLOG service]] service **using UDP networking**. | + | * Writes logging events to a remote [[dido:public:ra:xapend:xapend.b_stds:tech:ietf:syslog| SYSLOG service]] service **using UDP networking**. |
| * Writes logging events to a remoting sink using .NET remoting. | * 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. | * 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. | ||
| Line 50: | Line 45: | ||
| * 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. | * 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. | * Clients connect via Telnet to receive logging events. | ||
| - | vWrites logging events to the .NET trace system. | + | * 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. | * Sends logging events as connectionless UDP datagrams to a remote host or a multicast group using a UdpClient. | ||
| + | |||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||