A good log analizer?

Looking for a fast Log Analizer, need help =(

[micah_death]

Good Day!

I'm looking for a log analizer for IIS/Windows OS that is fast. My server log sizes are around 50-300Mb per day. (e.g. 1.14Gb for just under 2 weeks)

I need something FAST - most of what I see takes at least 24 hours to parse -- if it was made for windows.

I'd like my error URLs so I know what to fix. I'd also like my URL with query strings in them so I know what people are searching for. (We have our own search engine for our site.)

The more information I can get the better. (Preferably without the use of perl.)

Anyone know of any I can use?

Thanks!

PS
So far the Unix Webalizer is the best I've seen but it doesn't have all the features I like.

[wkitty42]

webalizer is what i use... IIRC, the source code is available so you can modify it or have it modified for your needs... and there's a windows flavor available so you don't have to run *nix if you don't want to...

not sure what you mean about the search terms showing up... they do on mine... they show up in the search terms section of the report... they just don't tell where those search terms came from (what engine)...

on the error urls, i just grep out the 400's seperately and then do what i need to do to fix them... again, i'm sure that a (slight?) modification of the source could fix that...

me? i use the OS/2 flavor as provided ;) i've got scripts that do everything else i need and they're all run automatically and the info is available when i want to look at it...

[micah_death]

Unfortunately Unix isn't like to well where I work (some security something, I don't understand it) and I am not a C/C++ programmer by any means so modifying source code would be major work...

I could use another program to find the 400s but was curious if something already exists and faster than the current ones I have tried.
(One program has been working for 42 hours and lacks at least 12hours longer...)

I'd even be satisfied with a list of differnet analizers so I can go and test each of them =) (Web Log Analizers finds odd stuff on google - search tips?)

We have no Unix computers where I work - it's all Windows

=)

[wkitty42]

as i said, there is a windows native version of webalizer available on their site... if you're not a coder, then that's about the best you can do... using additional programs on the log files is not a BadThing<tm>... in fact, it is a GoodThing<tm> in most cases...

[bcolflesh]

on the error urls, i just grep out the 400's seperately...

Good advice for really large logs - you can get a free Win Grep tool here:

wingrep.com/download.html

[micah_death]

That's probably what I'll do... (it's funny - MS people using Unix software ported to windows to get the job done!)

Thanks for your help and input.

=)