Versions Compared

Old Version 1

changes.mady.by.user Paul Berkowitz

Saved on

compared with

New Version 2

changes.mady.by.user Paul Berkowitz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The CardioLog Scheduling Service includes the following components:

  1. Usage Data Processing - Processes incoming tracking data from the Event Collector every hour.
  2. Portal Tree Updates - Retrieves the structure of the portal (ie., Monitored environments). This is done by creating an XML file which outlines the hierarchical structure of the portal, and then translates the XML data into relational data. This structure is the basis for data aggregations.
  3. Report Scheduling - Responsible for the automatic generation of all scheduled reports, and their distribution and publication.
  4. Active Directory Updates - Retrieves the list of all users and groups directly from Active Directory for use with visitor segmentation and other user targeted features.
  5. User Categories Updates - Retrieves the list of custom user categories from specific designated web services for use with visitor segmentation and other user targeted features.

Anchor
process
process
The Data Collection Process

  1. Download Tracking Code - The JavaScript The JavaScript tracking code is code is added to SharePoint using a the SharePoint feature (or a common page component such as master pages) and  and is downloaded to the client's browser with each page request.
  2. Personalize Content (Optional) - Information about the based on visitor segments is downloaded to the client's browser with each page request. The JavaScript code hides the content of the page, adds or modifies relevant page elements and finally re-then displays the custom page according to visitor segments.
  3. Track Usage Data - Information about user actions within the on website pages is sent to the CardioLogAgent web application - via the CardioLogAgent web application via asynchronous JavaScript calls (AJAX).
  4. Store Usage Data - The CardioLogAgent web application passes on the usage tracking information , via HTTP/S web requests , to the EventCollector web application - which , which writes the data into the CardioLog database.
  5. Process Usage Data - The Usage The Usage Data Processing service Processing service processes incoming tracking data from Event Collector (every hour by default)the EventCollector application. By default, this occurs hourly.
  6. View Usage Data - The processed data is visible in the Report Center and Analysis Center Report Center and Analysis Center. 

The data collected by CardioLog

is

includes page URL, query string, user name, date and time, browser type, operating system, workstation IP and WFE server IP.

 Tracking

 Tracking of usage data operates in a non-invasive transparent manner and

does

should not affect the monitored website's overall performance and response time. It is asynchronous to the monitored website's execution and

users'

user activity,

thus

and therefore has no direct impact on the monitored environment.

The

 The product has a marginal footprint on the website and can be turned off instantly should

a diagnosis be required

you require any site diagnosis.

 

JavaScript Tracking Code

Website usage tracking is performed by the Tracking Agent - , which is a 150KB piece of JavaScript code (out of which 75KB are optional), added to the , half which is optional. The code is added to all relevant website pages.

CardioLog Agent File

Bytes Sent

Bytes Received

/CardioLogAgent/AgentEmbed.aspx

/CardioLogAgent/ca.aspx (optional)

/CardioLogAgent/caUser.aspx (optional)

425

391

808

77668

70139

387

/CardioLogAgent/tunnel.aspx

1681

410

The download time for the Tracking Agent JavaScript code is dependent upon multiple factors - such as including network connectivity and band width. Generally, the download time is almost negligible.

The Tracking Agent JavaScript code is loaded on page document ready, and sends usage data to the CardioLog server - asynchronously. It can also be loaded on window onload. The calls to the CardioLog server do not affect the page response time.

In case of If there is a connection error, in order to avoid unwanted overhead, the tracking agent tries to reconnect after 60 seconds (configurable) in seconds in order to send usage data. The page will be displayed without modifications - if any - , assuming any were available, after 5 seconds (configurable).of no response. For more information see Tracking Agent Configuration.

Intlock encourages each customer to perform his/her their own performance tests.