Things that need doing:
- Read logfile location from metabase
- Allow working with multiple logfile folders
Anyway, here it is, if you find it useful I'd apprieciate a note. If you improve on it (which shouldn't be too difficult) please send me your copy so that I can learn from your improvements
7zip's command line version
the batch file itself
- You are running IIS 5 or later
- You have not modified the standard IIS logfile naming convention which is exAABBCC.log where AA= year, BB=month and CC is day.
- Open the 7zip download and extract 7za.exe to somewhere in your path (system32 for example)
- Place the batch file somewhere.
- Edit this line in the batch file: rem set iis logfile location
- Create a user with read access to the script and the 7za.exe and write access to your IIS log folder.
- Schedule the batch file under that user's credentials so that it runs every 1st of the month.
So that it points to your logfile folder
Of course It would be really easy to integrate a logfile analysis tool somewhere into this. I've had good experiences with WebLog Expert but anything that can be called from a command line should do nicely.
All this is tested on a few of my systems, it works there but I provide it with no warranty whatsoever. If you use it and your server is suddenly sucked into a wormhole and ends up in the dungeon dimensions it's your problem.