Browse by Tags

Tagged Content List
  • Blog Post: LOGPARSER #22: Domains referring traffic to your site

    SELECT    EXTRACT_TOKEN (cs(Referer), 2, '/') AS Domain,   COUNT(*) AS [Requests] INTO    ReferringDomains.txt FROM      logs\iis\ ex*. log GROUP BY    Domain ORDER BY    Requests DESC //Anders
  • Blog Post: LOGPARSER #21: Get bytes per extension

    This script will give you the amount of bytes sent by each file type, for example pictures, ASPX pages etc. Great if you need to work with size/performance. SELECT        EXTRACT_EXTENSION( cs-uri-stem ) AS Extension,     MUL(PROPSUM(sc-bytes),100.0) AS PercentageOfBytes...
  • Blog Post: LOGPARSER #18: Top 10 pages with most hits

    Will give you your top pages with most hits and some additional data. If your top 10 pages with most hits are the same as your top slow pages and/or largest you might want to do something about it. Select    TOP 10    STRCAT(EXTRACT_PATH(cs-uri-stem),'/') AS RequestPath,   ...
  • Blog Post: LOGPARSER #17: Get your broken links

    This script will give you site/page refers to your content though your content has moved. SELECT     DISTINCT cs(Referer) as Referer,     cs-uri-stem as Url INTO     ReferBrokenLinks.txt FROM     logs\iis\ex*.log WHERE     cs...
  • Blog Post: LOGPARSER #16: Remove those Compilation Debug=True from your prod server

    One thing I notice on several of my customers is that it really doesn’t matter how waterproof process you have for deploying web applications, and web.config files in particular. You’ll always end up with at least one web app somewhere with Compilation Debug = True. As you all know this hurts performance...
  • Blog Post: LOGPARSER #15: Check traffic from IP addresses

    Customer of mine used a hardware load balancer to distribute traffic between their frontend web servers. This script that I put together gave them a chance to check whether traffic was distributed evenly between servers (K’s, Hits), if average wait time was the same etc. 10.000 meter view what’s going...
  • Blog Post: LOGPARSER #14: TOP 20 pages with specific HTTP return code

    Digging into each ASPX page returning a specific error code. We used this script at a customer to get the pages with most 401 errors and also checked pages with most hits. You’ probably find these to be almost the same list. If you have Windows Authentication and your domain used NTLM instead of Kerberos...
  • Blog Post: LOGPARSER #13: Page types with large bytes sent

    This is a great script for checking what page types are causing bytes sent SELECT     EXTRACT_EXTENSION(cs-uri-stem) AS PageType,     SUM(sc-bytes) as TotalBytesSent,     TO_INT(MUL(PROPSUM(sc-bytes), 100.0)) AS PercentBytes     INTO PagesWithLargestBytesSent...
  • Blog Post: LOGPARSER #12: Troubleshoot who is causing your 500 errors?

    This script is very interesting tracking down specific users causing errors in your IIS environment. Could be a physical person or a tool configured to run under a domain account. One of my customers had a tool for checking site availability and it was pinging several pages constantly (SLA check). What...
  • Blog Post: LOGPARSER #11: Megabytes sent per HTTP status code

    This script checks amount of bytes sent for different pages and different sc-status. SELECT     EXTRACT_EXTENSION(cs-uri-stem) AS PageType,     SUM(sc-bytes) as TotalBytesSent,     TO_INT(MUL(PROPSUM(sc-bytes), 100.0)) AS PercentBytes     INTO...
  • Blog Post: LOGPARSER #10: Check your substatus codes

    If you find out that you have a large number of sc-status codes, e.g. 401, it could be an idea to check the sc-substatus codes. SELECT     sc-status,     sc-substatus,     Count(*) AS Total     INTO 401subcodes.txt FROM     logs...
  • Blog Post: LOGPARSER #9: Check your Win32 errors trends

    This script will get you any win32 errors within you IIS logs. SELECT     sc-win32-status as ErrorNumber,     WIN32_ERROR_DESCRIPTION(sc-win32-status) as ErrorDesc,     Count(*) AS Total     INTO Win32ErrorNumbers.txt FROM    ...
  • Blog Post: Logparser #8: Know your Error trends

    This is a script I used at one customer to help the site developers know if any of the recent deployed updates had any affect on the site errors. SELECT   TO_STRING(To_timestamp(date, time), 'MMdd') AS Day,   SUM(c200) AS 200s,   SUM(c206) AS 206s,   SUM(c301) AS 301s,   SUM...
  • Blog Post: LOGPARSER #7: Average time taken per user

    Why is this interesting? One of the site developers at one of my customers approached me and said that “Hey, you know we have a couple of internal users who complain about our website performance. They say its always slow and takes forever for pages to load….”. My response was “Ok, what data do you have...
  • Blog Post: LOGPARSER #6: Check daily bandwidth

    This script checks for daily bandwidth. Great for spotting trends. Select      To_String(To_timestamp(date, time), 'MM-dd') As Day,      Div(Sum(cs-bytes),1024) As Incoming(K),      Div(Sum(sc-bytes),1024) As Outgoing(K) Into BandwidthByDay...
  • Blog Post: LOGPARSER #5: Top 10 slowest ASPX pages

    Top 10 pages with the longest time-taken SELECT TOP 10 cs-uri-stem, max(time-taken) as MaxTime, avg(time-taken) as AvgTime INTO toptimetaken.txt FROM logs\iis\ex*.log WHERE extract_extension(to_lowercase(cs-uri-stem)) = 'aspx' GROUP BY cs-uri-stem ORDER BY MaxTime DESC Top 10 pages with the longest...
  • Blog Post: LOGPARSER #4: Top 10 largest ASPX pages

    Script for checking your largest pages. Maybe you can reduce the size of these pages? Good to know before a performance test etc Select Top 10 StrCat(Extract_Path(TO_Lowercase(cs-uri-stem)),'/') AS RequestedPath, Extract_filename(To_Lowercase(cs-uri-stem)) As RequestedFile, Count(*) AS Hits, Max(time...
  • Blog Post: LOGPARSER #3: Unique users per day

    This is a combination of two scripts you need to use to get the unique number of users each day. This is for Logparser 2.2 and earlier if i remember correct. Maybe later version will give you this in another way. I’ve seen a variety of samples out there but this is the only true way I know if getting...
  • Blog Post: LOGPARSER #2: Know what browsers your users have

    This script will give you all the browser types hitting your site, order by most used. SELECT distinct cs(User-Agent), count(*) as hits INTO useragentsalltypes.txt FROM logs\iis\ex*.log GROUP BY cs(user-agent) ORDER BY hits DESC //Anders
  • Blog Post: LOGPARSER #1: Top 10 images by size sent

    This script is an easy way of checking if any of your pictures take up too much bandwidth on you site. Maybe you can resize them or change resolution?  Select   Top 10   StrCat(Extract_Path(TO_Lowercase(cs-uri-stem)),'/') AS   RequestedPath,   Extract_filename(To_Lowercase...
  • Blog Post: LOGPARSER #0: Get started with logparser

    I’ve used Logparser on several occasions at my customers and it’s always fun to show just how much valuable info you can dig out by this free tool. Many developers have notused Logparser and don't know its capabilities and I also often discover that developers don’t know their sites well enough once...
Page 1 of 1 (21 items)