<div dir="ltr"><div><div><div><div><div>check this site for an idea:<br><br><a href="http://www.w3.org/Daemon/User/Config/Logging.html">http://www.w3.org/Daemon/User/Config/Logging.html</a><br><br></div>I find apache logs very easy to parse with many tools.<br>
<br></div>Another way to look at this is from the viewpoint of someone having to understand why the apps are not working as they think they should. What type of data would help? At that point, the data type will usually dictate an output format. And sysadmins _LOVE_ error messages like:<br>
<br></div>application foo received 0x120BAF02 at 0x33BD000001A1. Is this OK?<br><br></div>That is useless! Saw that (different addresses) during a Debian install once. I thought my head would explode.<br><br></div>I've seen many java applications (java is a great drink and a country I've never visited. It's a crappy language that should not be taught - grr) that split up logs into sort of a user/admin general process, admin error, and application error tracking. Each had a deeper level of details with very long time stamps.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 28, 2013 at 6:34 PM, Robert L. Harris <span dir="ltr"><<a href="mailto:robert.l.harris@gmail.com" target="_blank">robert.l.harris@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div> 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.<div>
<br></div><div> 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?</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div>Robert</div><div><br clear="all"><div><br></div>-- <br>:wq!<br>---------------------------------------------------------------------------<br>Robert L. Harris<br><br>DISCLAIMER:<br> These are MY OPINIONS With Dreams To Be A King,<br>
ALONE. I speak for First One Should Be A Man<br> no-one else. - Manowar
</div></font></span></div>
<br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>-- <br>James P. Kinney III<br><i><i><i><i><br></i></i></i></i>Every time you stop a school, you will have to build a jail. What you
gain at one end you lose at the other. It's like feeding a dog on his
own tail. It won't fatten the dog.<br>
- Speech 11/23/1900 Mark Twain<br><i><i><i><i><br><a href="http://electjimkinney.org" target="_blank">http://electjimkinney.org</a><br><a href="http://heretothereideas.blogspot.com/" target="_blank">http://heretothereideas.blogspot.com/</a><br>
</i></i></i></i>
</div>