Hi David

We're seeing the usual trauma of massive log files as the result of increased traffic. We've recently crossed the line from where this was inconvenient to where it has become a serious problem. Our "quick and dirty" solution was to post-process our logs and strip out all logged requests for images. While this hack solution is getting us by for right now - I would prefer something more elegant, sustainable and scalable.

I have been trying to figure out if there is any way to simply not log *.gif, *.jgp, *.css and *.js. So far I cannot seem to figure this out.

Any help would be really appreciated!


IIS supports fine-grained control of which resource access results in a log entry. You simply need to set the DontLog property at the corresponding URL-level, and IIS will ignore logging requests to that URL or virtual directory. See the following blog entry for related details.

However, there is no configuration syntax to direct IIS to simply never log access to *.gif, *.jpg, *.css, and *.js regardless of location... but that should not be a big deal for a well-organized website. Presumably, you have all your resources organized and categorized across your website for efficient resource management - for example, all images are available under a /images virtual directory, all stylesheets under a /stylesheet virtual directory, and all client-side Javascript under a /client-scripts directory.

If your website content is organized, then you can simply set "DontLog" for the /images, /stylesheets, and /client-scripts virtual directories, and none of those resources will get logged by IIS.

Otherwise, you have no choice but to set DontLog property as a IIsWebFile for every single scattered resource on your web server. While IIS supports direct configuration of DontLog on a granular per-URL scope via the logic of "If URL Resource has DontLog set to true, then do not log access to it", you really want a meta-configuration-logic of "If the URL Extension is X, Y, Z, then set DontLog to true."

Ideally, you want to execute your meta-configuration-logic via an add-on extensibility module to either the IIS Configuration System or IIS Core Web Server. However, in this case, decision to Log a request is static, so you cannot use IIS Core Web Server extensibility mechanisms like ISAPI Filter to dynamically add your logic. IIS Configuration System does not support this rare form of extensibility, either...which means your only alternative is to write a script that automatically (but statically) updates the DontLog properrty of URLs your website on your behalf.