Log Parsing - Near Real Time

Oscar Fernandez oscaretu at gmail.com
Tue Aug 2 11:13:48 UTC 2011

You can apply "split" to the output of "tail"j to generate files of with the
same number of lines, that you would process with the program that extracts
the intereresting data from them:

       split - split a file into pieces

       split [OPTION]... [INPUT [PREFIX]]

       Output fixed-size pieces of INPUT to PREFIXaa, PREFIXab, ...; default
size is 1000 lines, and default PREFIX is `x'.  With no INPUT, or when INPUT
is -, read standard input.

       Mandatory arguments to long options are mandatory for short options

       -a, --suffix-length=N
              use suffixes of length N (default 2)

       -b, --bytes=SIZE
              put SIZE bytes per output file

       -C, --line-bytes=SIZE
              put at most SIZE bytes of lines per output file

       -d, --numeric-suffixes
              use numeric suffixes instead of alphabetic

       -l, --lines=NUMBER
              put NUMBER lines per output file

              print a diagnostic just before each output file is opened

       --help display this help and exit

              output version information and exit

       SIZE may have a multiplier suffix: b 512, kB 1000, K 1024, MB
1000*1000, M 1024*1024, GB 1000*1000*1000, G 1024*1024*1024, and so on for
T, P, E, Z, Y.

On Mon, Aug 1, 2011 at 5:48 PM, Akins, Brian <Brian.Akins at turner.com> wrote:

> You could use something like syslog-ng that can "tail" the log file and run
> them through a script.
> --
> Brian Akins
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

Oscar Fernandez Sierra
oscaretu at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20110802/b7cc7ba3/attachment.html>

More information about the nginx mailing list