[ale] Log parsing/alerting tool recomendations
Wolf Halton
wolf.halton at gmail.com
Tue May 28 21:20:33 EDT 2013
I am interested in what kind of tools people are using. I am parsing
security logs, and writing my own scripts to output csv. I think the more
general the parsing tool, the better, and a feature I really like is
pushing the finished product to the end user by email.
Wolf Halton
--
http://wolfhalton.info
Apache developer:
wolfhalton at apache.org
On May 28, 2013 6:36 PM, "Robert L. Harris" <robert.l.harris at gmail.com>
wrote:
>
> I'm working with a number of developers trying to create a logging
> standard for some apps and devices my company is developing. Most of them
> are linux based and running syslog-ng so we have some flexibility and can
> standardize. The big concern though is coming up with a format for the
> logs for the tools we will (may) be using to parse the data. Personally I
> like the idea of using cmd line and piping unix utils.
>
> A recommendation was thrown out though to ask about how others are
> parsing system and application logs to look for issues, tracking, etc and
> what kinds of input they take (json, xlm, .log, etc). Anyone have any
> tools you're using that are just incredible and what kinds of input they
> can work with?
>
> Robert
>
>
> --
> :wq!
> ---------------------------------------------------------------------------
> Robert L. Harris
>
> DISCLAIMER:
> These are MY OPINIONS With Dreams To Be A King,
> ALONE. I speak for First One Should Be A Man
> no-one else. - Manowar
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20130528/2896061f/attachment.html>
More information about the Ale
mailing list