Download logFaces User Manual

Copyright ©2009-2013 Moonlit Software Ltd, All rights reserved
2.9.2.1
Log4j receivers
Log4j receivers process XML logs transmitted by socket appenders. They can operate over TCP or
UDP protocols and will expect XML schema compliant with log4j DTD. In fact there is a whole array
of frameworks using this format, not only Java appenders. You will find appenders in Python, Perl,
PHP, .Net using exactly the same format.
Typical form for adding new or modifying existing log4j receiver is shown below:
Figure 2.9.3: Adding log4j receiver
Enabled
Description
Makes receiver active or non-active. Not active receivers will stay in the list but will not work.
Friendly description or title of receiver, for management purposes only
Protocol
Type of protocol to use – TCP or UDP
Address
If server is installed on a computer with several network cards, you can bind server sockets to a
particular address or a host name. This is a good idea if you need physical separation of the
transport. When 'any-address' is specified, the server will pick the default binding, this will allow
access to server by any address it supports. Otherwise, the access will be strictly by the address
you select.
Port
Time
Listening port, make sure it's available before enabling the receiver
Which time stamp to use for received log events – the one originating from the source, or the
server local time. Use this option when there are many sources and there is no time server to unify
the times across the applications.
20