I saw some extra traffic on my website last week, and as an old school IIS guy I wanted to run Log Parser against my website logs. In Azure Websites, the traditional IIS logs are stored at %home%\Logfiles\http\RawLogs, those are of W3C format. Azure Web sites now has a lot of cool Site Extensions like ‘Analog HTTP Log Analyzer’, ‘IIS log file analyzer’ which gives you a report based on your website logs. However, there are certain times you want to run the log yourself running custom queries.
I wanted to run the sweet old LogParser against these logs, and started downloading the logs from the %home%\Logfiles\http\RawLogs. I was thinking why not run LogParser right in the box that’s hosting my Web site, since I’ve got the Kudu console, also from the new Azure Portal (preview) (cmd/powershell). Viola! I transferred the LogParser installation folder from my local machine (C:\Program Files (x86)\Log Parser 2.2) to my Azure Website (under D:\home\Diagnostics\LogParser), and it just worked!
Now, I can run any custom logparser script that I’m used to right inside the Kudu console, or from the new Azure preview Portal. Saves a lot of time, and of course bandwidth to download those files