I want to monitor IIS at the per-request level for bandwidth usage, and subsequently filter by application and/or app pool to produce summaries at certain intervals that I can push out to loggers. Any tips?
I want to monitor IIS at the per-request level for bandwidth usage, and subsequently filter by application and/or app pool to produce summaries at certain intervals that I can push out to loggers. Any tips?
To err is human. To really foul things up ... you need a computer.
I'm pretty sure that the standard IIS logs include the size of transfer (in KBytes?) as part of the logging, so presumably it'd be a case of either importing the IIS log files into a custom system for analysis, or having IIS log directly into a database (which I'm pretty sure you can set up). You should then be able to analyse the logged data and extract the information you need.
That said, I've not tried to do this myself, so it might be harder than a think...
edit: having had a quick check on our Web Server 2k8 R2 box, it looks like you *can't* log directly to a database (*sigh*), so finding some way to automatically import the data from the text-based log files will be easiest...
You should be able to log direct to a database. You just need to enable to ODBC logging feature under the application server role.
Not sure if this is restricted under Web Server 2k8R2, but you certainly should be able to under the full fat version.
scaryjim (17-02-2012)
There are currently 1 users browsing this thread. (0 members and 1 guests)