Page History
The fine tuning process is essential 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 perform the fine tuning processfine tune your system.
CardioLog collects usage data for various event types (, including views, visits, duration, search etc.). , and most other ways a user can interact with your site. The Usage Data Processing service component matches events to their the corresponding item in your SharePoint tree item. An Any event which has associated with a URL that does not match any item in your tree item (for instanceeg., a A URL address which includes a list of custom parameters, or a URL which is not part of the your monitored environments) is called known as a " Lost Event". Lost events are not displayed in the reports' results by default, they . Report results do not display lost events by default. They appear only after fine tuning the data.
Tuning Fine tuning the data includes of the following steps:
- Determining which data should not be collected and defining data collection filters.
- Identifying Lost Events and defining URL address modifications.
It is recommended to perform this process about a month after the initial installation of in the production environment, 2-3 weeks after an upgrade, and 2-3 weeks after adding a any new monitored environment to CardioLog.Fine 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.
Contents
Anchor identifying lost identifying lost
Identifying Lost Events
| identifying lost | |
| identifying lost |
1. Execute the following SQL script against the CardioLog database to get a list of the lost events event URLs. This can be done for a specific date range (edit the date range by editing the timestamp in the SQL query):
| Info | ||
|---|---|---|
| ||
Use CardioLog select SearchURL, count(SearchURL) |
...
timestamp >= '2010-09-01 00:00:00' /* Edit start date (date format: YYYY-MM-DD) */ |
...
eventtype = 0 |
Query results example:
| Info | ||
|---|---|---|
| ||
/* 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 reason reasons for the missing URL:
- URL with custom parameters
- URL with an internal server name (, instead of FQDN)
- URL with a non-secure channel (, instead of a secure channel and vice-versa)
- URL for from a non-monitored environment
3. Create URL mappings Mappings based on Regular Expressions (See how to create URL Mappings). Examples. Examples:
- URL with custom parameters:
pattern: "aspx\?department=.*"
action: "aspx"
- URL with an internal server name (, instead of FQDN):
pattern: "http://websrv01/(.*)"
action: "http://www.intlock.com/${1}"
- URL with a non-secure channel (, instead of a secure channel and viceor vice-versa):
pattern: "http://www.intlock.com/(.*)"
action: "https://www.intlock.com/${1}"
- Data for URLs for from a non-monitored environment (external) or administration pages (under /_layouts) can be seen in the "Page Views By URL" and "Unique Users by URL" reports.
Anchor fixing lost fixing lost
Fixing Lost Events
| fixing lost | |
| fixing lost |
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 the your URL Mappings. The following example replaces the internal server name with the FQDN (edit Edit the start date timestamp in the SQL query to a relevant date range for you).
Create a script based on this example to fix history data according to for the URL Mapping you have created and . Then execute it against the CardioLog database.
| Info | ||
|---|---|---|
| ||
/* Example: Replace the internal server name to the portal name - |
...
...
...
*/ |
Use CardioLog |
...
int |
...
datetime |
...
10000 |
...
Edit the start date (date format: YYYY-MM-DD) */ |
...
where |
...
update |
...
a |
...
SearchUrl = substring(replace( |
...
SearchUrl, 'http:// |
...
websrv01/','http://www.intlock.com/'), 0, 400) |
...
GO |
3. Execute Execute the following SQL script against the CardioLog database to map the Lost Events lost events to their corresponding SharePoint tree item. This can be done for a specific date range (edit editing the date range timestamp in the SQL query):
...
| Info |
|---|
GO
/********************************************************************************/
/**** Fix Lost Events *****/
/********************************************************************************/
IF NOT EXISTS (SELECT name FROM sysindexes WHERE name = 'idx_tab_event_log_temp_for_update')
create index idx_tab_event_log_temp_for_update on tab_event_log(entityId, eventLogId) include (timestamp, eventType, entityType)
GO
declare @startTime datetime
declare @endTime datetime
declare @top int
declare @rowsupdated bigint
declare @continue smallint
declare @EventLogId bigint
...
| ||
USE [CardioLog] DECLARE @RC int set @startTime = '2010-09-01' |
...
drop index tab_event_log.idx_tab_event_log_temp_for_update
/* Delete reporting data cache */
delete from tab_controls_cache
print 'Done'
/* Edit start date (date format: YYYY-MM-DD) */ |
...
select @continue = @@ROWCOUNT
while @continue > 0 begin
...
EXECUTE @RC = [dbo].[stp_eventlog_fix_lost_events] |
| Anchor | ||||
|---|---|---|---|---|
|
The SharePoint Tree Auto Automatic Fine Tuning service is used in order to map maps SharePoint URLs to the their corresponding object in your SharePoint tree object in automatically. All items can then be accessed using the Object Explorer automatically. For instance, if If users access a SharePoint website through different zones (public URL'sURLs), or to 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 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 the your SharePoint WFEs), and then maps them by their SPID in within the tree structure.
Starting version 2.0.6.0, the The SharePoint Tree Auto Automatic Fine Tuning web service is installed with the CardioLog Analytics SharePoint feature by default.
Manual Installation
Perform the following steps for every SharePoint WFE:
...
- Web.config
- SpidFinder.asmx
...
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):
| Info | ||
|---|---|---|
| ||
<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"
Anchor refreshing refreshing
Refreshing
| refreshing | |
| refreshing |
...
Report
...
Data
- Clear the reports report data cache:
Go to CardioLog > From the navigation pane in CardioLog, go to Administration > System Configuration > Reporting Data and click on Clear Cache OR execute the following SQL script against the CardioLog database:
- Delete history
- Delete existing versions of the report :
Go to CardioLog > Report Center, click the by using the navigation pane in CardioLog, and clicking on Report Center. Click the relevant report and click on Delete Historical Data. - Regenerate reports:
CardioLog . CardioLog reports are generated automatically by the Report Scheduling service. To regenerate a report on your own, click the report and select Open, then click Generate Report from the actions menu.