Re: analysis of java application logs
CncShipper wrote:
I wrote one of these and thought about Open Sourcing it, but lost
"open sourcing"
interest. I parsed the logs into a db, and assigned id's to the
"DB, "IDs" (no greengrocer's apostrophe, and "id" is a different word from
"ID", although the meaning you imputed by the substitution is poetic and
interesting)
various fields.
You could then search by Type, ( WARNING, SEVERE, etc... )
"type"
You could search a range of times
It could handle multiple log files into one run
could Sync on an event and stop analyzing on another trigger
"synch"
Graphs to count trends, events, exceptions
"graphs"
Used Reg-Ex a heck of a lot of work.. Sorted all the transactions in
"used" "regex"
the logs, so you could also display by package name, really helped
me solve a lot of problems when I was working .. took me nearly two
years to complete everything to where it is today..
Double-dot, or two consecutive periods, is not legitimate punctuation in lieu
of a comma or full stop.
I never found a package that even came close to it.. which is why I
wrote it
You have made an important and useful point. Covering for a bad log format is
a freeform-text parsing problem, inherently difficult and heuristic and
probably never perfect. I wonder if your effort would have been better spent
converting to a log format that is parser-friendly, as the OP should do.
--
Lew
Honi soit qui mal y pense.
http://upload.wikimedia.org/wikipedia/commons/c/cf/Friz.jpg