Hi Daniel, Here is a magazine article I wrote on that some time back. I like syslog or whatever replaces it. http://www.jaxmag.com/itr/online_artikel/psecom,id,766,nodeid,147.html
I am hoping that there is some framework like log4j that just needs its configuration file updated. That is definetly a question for the hard working devs to answer. The real cost is that valuable information is probably not getting used as it is hidden in the noise that we call the error.log There are a number of scenarios: You could run the analyzer from Jenkins and scp the days log at some scheduled moment. Jenkins could then decide if it wants to warn people if some value is hit like unknown defect, too many slow queries etc. Run before and after a bug bash to find new defects As a developer to see if you have introduced new bug patterns Or just nightly. The script takes about 5-10 seconds for 1 GB on my average desktop. Adding ten lines of code would allow it to parse all logs in a directory. Its only valuable if we systematically review for new bug patterns as the product is released. Regards, Alan Alan Berg Group Education and Research Services Central Computer Services University of Amsterdam ________________________________________ From: Daniel Parry [[email protected]] Sent: 18 May 2012 15:45 To: Berg, Alan Cc: [email protected] Subject: Re: [oae-dev] Log parsing and introductions. Hi, Vaguely related, it would be ace if it were easy to pump the OAE logs into syslog and store them off the app server box as I'd be nervous of churning up disk IO running a log analyzer locally against a large volume of log data. Best wishes, Daniel -- --| Daniel Parry: [email protected]. www.caret.cam.ac.uk/ |-- "Your character is your most effective means of persuasion." [John C. Maxwell] _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
