Re^2: Big hairy ugly log sorting merging problem

*sigh*

Yep, I realized not too long after posting that straight sorting would be folly... Log entries that occur during the same second shouldn't necessarily be sorted by anything; they should simply preserve whatever order they had in their original files.

Apon realizing this, I started basically the above, hoping that my inherent laziness would be fed by someone elses' apache log merging script ("Here ya go, little guy!").

If I finish before an entire script magically appears in the comments below, than if someone wants it, just reply your intent.

That way, the saints (like merlyn) can point and laugh, too! :)

As a side note, wouldn't it have been cool to have mod_perl spin those logs off to the database server, into their own tables? Maybe my boss will pay me to write that...

Comment on Re^2: Big hairy ugly log sorting merging problem

Replies are listed 'Best First'.
Re^3: Big hairy ugly log sorting merging problem by Aristotle (Chancellor) on Aug 07, 2004 at 01:44 UTC
Actually, there are modules (in the Apache as well as Perl sense of the word) to dump logs to a database instead of a file. Depending on the amount of traffic you get, using them may or may not be wise. Makeshifts last the longest.	[reply]
Re^4: Big hairy ugly log sorting merging problem by mr. jaggers (Sexton) on Aug 07, 2004 at 02:02 UTC
Well, hundreds of megs per month for several virtual hosts... I think this sounds like more of a gut-feeling hardware requirement issue. I know that I wouldn't trust my off-the-cuff guess. I suppose I could profile individual insertions and make a judgement based on hit rate... Has anyone seen any performance numbers or hardware suggestions?	[reply]