Microsoft LogParser provides the SharePoint administrator with significantly greater usage analysis capabilities than those previously offered in SharePoint 2010 and much much more so than offered in 2013, which are minimal and problematic. This posting captures the steps undertaken in analyzing simple website usage metrics using Microsoft Log Parser. Specifically, it captures the steps for generating usage graphs based upon IIS data, including Daily Total User Requests (Page Hits).
Note down these accounts, both in their claims-aware format (eg, 0#.w|DOMAIN\Account) and their standard AD format (eg, DOMAIN\Account). Both forms may appear in the IIS logs and both would need to be filtered out so as to focus on actual user metrics.
Note: I've organized the log files in this manner so as to facilitate analyses using Log Parser. It was the most rapid way I could think of at the time for building the metrics that I wanted by month.
Note: Tailor the where clause to filter out those service accounts generating a lot of hits but that do not generate meaningful usage data from a user usage perspective. Same for the setup user administrator account, which is used by the farm administrator to administer configuration. Note: Some users, who leave a browser connected to SharePoint for long periods, may generate anomalously large hits. For example, on one day during the entire month, one user generated 547,233 hits, almost all of it to [site]/vti_bin/sites.asmx. Filtering out such results reduced the total hit count for that day to a level consistent with previous results.
cs-username<>NULL
logparser -i:IISW3C "select count(*) as ct,EXTRACT_TOKEN(cs(user-agent),0,'/') as agent from *.log group by agent order by ct desc"
logparser logparser -i:IISW3C "select count(*) as ct,EXTRACT_TOKEN(cs(user-agent),0,'/') as agent into MyFile.txt from *.log group by agent order by ct desc"
logparser -i:IISW3C "select count(*) as ct,EXTRACT_TOKEN(cs(user-agent),0,'/') as agent from *.log group by agent order by ct desc" -q > MyFile.txt