In order to ensure qualitative and accurate data, it is ideal to go through the fine tuning process on your system. This section provides detailed instructions on how to fine tune your system.
CardioLog collects usage data for various event types, including views, visits, duration, search, and most other ways a user can interact with your site. The Usage Data Processing service component matches events to the corresponding item in your SharePoint tree. Any event associated with a URL that does not match any item in your tree (eg., A URL address which includes a list of custom parameters, or a URL which is not part of your monitored environments) is known as a Lost Event. Report results do not display lost events by default. They appear only after fine tuning the data.
Fine tuning the data includes the following steps:
It is recommended to perform this process about a month after the initial installation in the production environment, 2-3 weeks after an upgrade, and 2-3 weeks after adding any new monitored environment to CardioLog. Fine tuning should be performed by a user with a local administrator account on the CardioLog server and with a CardioLog Administrator role. Contact us for further assistance.
1. Execute the following SQL script against the CardioLog database to get a list of lost event URLs. This can be done for a specific date range by editing the timestamp in the SQL query:
select SearchURL, count(SearchURL)
Query results example:
/* Example #1: URL with custom parameters */
2. Check if the URL matches a SharePoint tree item. If it does not match, identify one of the reasons for the missing URL:
3. Create URL Mappings based on Regular Expressions. Examples:
1. Make sure that there is a full backup of the CardioLog database before you continue to the next step.
2. Fix your history usage data according to your URL Mappings. The following example replaces the internal server name with the FQDN (Edit the timestamp in the SQL query to a relevant date range for you).
Create a script based on this example to fix history data according for the URL Mapping you have created. Then execute it against the CardioLog database.
/* Example: Replace the internal server name to the portal name - http://websrv01/ > http://www.intlock.com/ */
3. Execute the following SQL script against the CardioLog database to map the lost events to their corresponding SharePoint tree item. This can be done for a specific date range editing the timestamp in the SQL query:
DECLARE @RC int
set @startTime = '2010-09-01' /* Edit start date (date format: YYYY-MM-DD) */
EXECUTE @RC = [dbo].[stp_eventlog_fix_lost_events]
The SharePoint Tree Automatic Fine Tuning service maps SharePoint URLs to their corresponding object in your SharePoint tree automatically. All items can then be accessed using the Object Explorer. If users access a SharePoint website through different zones (public URLs), or SharePoint pages with custom parameters, this service will map the different URLs into a single corresponding SharePoint object, bypassing the need to manually create an entry for multiple variations of the same item in the URL Mappings module.
Each SharePoint object in the SharePoint tree structure has a unique SharePoint object ID, known as an SPID. The Portal Tree Updates service component retrieves all lost events and sends them to the SPIDFinder web service, located on your SharePoint WFEs, and then maps them by their SPID within the tree structure.
The SharePoint Tree Automatic Fine Tuning web service is installed with the CardioLog Analytics SharePoint feature by default.
To enable/disable the SharePoint Tree Automatic Fine Tuning web service, edit the [CardioLog Installation Folder]/CardioLogScheduleServices/CardioLog.Services.exe.config (located on the CardioLog application server):
<add key="RunSpidFinder" value="true"/>
You can test the Web Service by browsing /_layouts/CardioLogAgent/SpidFinder.asmx and invoking the GetSPIDbyURL method. Submit the URL for your SharePoint website homepage, and verify that the guide value is not "00000000-0000-0000-0000-000000000000"