Page History
...
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.
Contents
...
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:
| 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 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 from a non-monitored environment
...
- 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 or vice-versa:
pattern: "http://www.intlock.com/(.*)"
action: "https://www.intlock.com/${1}"
- Data for URLs 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.
...
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.
| 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 to their corresponding SharePoint tree item. This can be done for a specific date range editing the 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 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.
Starting with 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 Report Data
| refreshing | |
| refreshing |
- Clear the report data cache:
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 from tab_controls_cache
Delete existing versions of the report by using the navigation pane in CardioLog, and clicking on Report on Report Center. Click the relevant report and click on Delete Historical Data. - Regenerate reports. 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.