The 'Log' tag is used to defined a log. As I said before, a log is not just an ASCII file, it is a set of line, so log managed by Kazimir can be of
several types. As all Kazimir objects, a log as a name that must be used to identify the log object in the config file.
The keyword for 'Log' are:
Name : The name of the log object. Mandatory
Type : the type of the log. Mandatory. It can have the following values:
ASCII : the log is a regular ASCII file
CMND_OUT : the log is the stderr and stdout of an external command. An additional keyword UpdateInt exists. If the external command ends, it is relaunched after UpdateInt seconds.
COROUTINE: the coroutine is very similar to the CMND_OUT, the only difference is that a coroutine is never re-spawned.
TCPCLIENT: the log is what we read from a TCP client socket
Path : the path of the log. Mandatory. This is not necessary a pathname, it could be a network address or a command line. For each type, the syntax will
differ:
with a ASCII log, 'Path' should be a regular path, for example /var/adm/messages
with a COROUTINE or CMND_OUT, 'Path' is a command line, for example 'binary_log_interpreter.pl /var/my_log.binary'
with a TCPCLIENT, 'Path' as the shape
, for example 'daytime@localhost', '13@127.0.0.1', '13@localhost' or 'daytime@127.0.0.1'
UpdateInt : the time to wait between two run of a log defined by a command line. This is a postfixed time value (see below). Optional, default value is 5 minutes.
TimeFormat: the format of the time representation in the log. This keyword is a little more touchy, so I dedicated a subsection to it. Optional, default value is NONE.
, for example 'daytime@localhost', '13@127.0.0.1', '13@localhost' or 'daytime@127.0.0.1'