Page History

The IIS Logs Import feature allows you to gather your existing usage tracking data, dating from before the installation of installing CardioLog Analytics. This is done by importing the information from IIS logs.
Note: Log entries are imported as is (URL mappings and/or username normalization do not apply) and are counted towards the page views license quota.

1. Run Services.msc on the CardioLog application server, and then stop CardioLog Scheduling Service.
2. In the Administration tab, the navigation pane in CardioLog, under Administration, click IIS Logs Import
3. If you receive an error that you need to install Log Parser, download version 2.2 or newer and install it on the main CardioLog Server.
   
   Image Modified
   IIS Logs Import LogParser Error
    
4. Select the web site you would like to import from and confirm that the Log File Directory is accurate.
5. Fill out the directory path of the IIS logs files for the SharePoint web site.
   Note: It is recommended to copy the log files to the CardioLog server. If you have more than one SharePoint WFE, you will need to repeat the import process for each WFE.
6. Make sure to import a single IIS log file at a time in order to avoid errors and/or large tempdb transactions.
7. Make sure that prior to importing IIS log, the system requirements are fully met, specifically the CardioLog database should be on a dedicated SQL Server instance. 
8. Select the desired date range for the logs you would like to import
   Note: Please choose dates prior to the CardioLog installation, or dates in which the CardioLog tracking agent was down. Choosing overlapping dates subsequent to these dates will result in duplication of usage tracking data. IIS Logs Import Main Window
   Note: You may need to create a network share in order to access your WFE (Web Front End). If you have more than one WFE, you will need to repeat the import process for each WFE.
   

9. For more options, click on Show Advanced Settings.

10. Under Included File Extensions, add all commonly used file extensions in the portal (ieeg. MS , Office documents, videos etc.). Use the Enter key as a separator.
    
    

    Info
    icon false title Sample list of common file extensions
    aspx html htm txt doc docx ppt pptx xls xlsx wmv avi mov

    
    Note: It is recommended to import specific file extensions, rather then importing all file extensions as IIS logs contain log entries for scripts, web services, icons, css files, and other files that are not relevant to usage analytics.
    
    Image Added
    IIS Logs Import Main Window

     

11. For more options, see Advanced Settings.

12. Under Excluded User Accounts, add those SharePoint service accounts that you wish to exclude from the import process. These should be formatted thus: DOMAIN\Username. Use the Enter key as a separator.Click the Import

13.  button Under Excluded User Agents, add bots and spiders which generate non-human activity.
    Note: The Share Point search engine crawler is excluded by default.

14. Click the Import button to begin importing the usage data from IIS.
    

15. Once all logs were imported, log in to CardioLog execute the following scripts in the following order against the CardioLog database to map the data (edit the date range):
    1. Map IIS Logs events to tree
    2. Map IIS Logs events to user groups 
    3. Map IIS Logs to user categories
16. Log in to the CardioLog application server, run Services.msc and start CardioLog Scheduling Service.