System Architecture


CardioLog Analytics Architecture

 It is recommended to install the CardioLog Analytics application on a dedicated server and the CardioLog Analytics database on a dedicated SQL Server instance.

The CardioLog Analytics application and database can be installed on-premise, on physical servers or virtual machines, or hosted on Microsoft Azure virtual machines (Iaas) which meet the hardware and software requirements and with the required ports and permissions.

The following architecture diagrams display a common implementation of CardioLog Analytics hosted on-premise and on Microsoft Azure virtual machines (IaaS).

CardioLog Analytics hosted on-premise


CardioLog Analytics hosted on Microsoft Azure



When hosting CardioLog Analytics on Microsoft Azure virtual machines (IaaS) and tracking a SharePoint on-premise farm, a site-to-site VPN is required.

CardioLog Analytics System Components

The CardioLog Analytics solution includes the following components:

A web application for configuring and viewing the web analytics reports.

 User Interface

A repository (SQL database) for storing all tracking and reporting data.


A web service which provides the structure of the monitored website.

 Website Tree Service 

A SharePoint solution which embeds a JavaScript tag to all website pages, monitors site usage and personalizes site content. 

 Tracking Agent  

A web service which sends tracking data from the tracking agent to the CardioLog database.

 Event Collector

A Windows service which runs scheduled jobs, such as usage data processing, importing website tree structure and user information. 

 CardioLog Scheduling Service 



A Windows service used to run health checks of the CardioLog system.

 CardioLog Diagnostics Service

All components are hosted on the CardioLog application server except the database which is hosted on the CardioLog SQL server and the Tracking Agent which is hosted on the monitored environment.

The CardioLog Scheduling Service includes the following system jobs:

  1. Usage Data Processing - processes incoming tracking data from Event Collector every hour.
  2. Portal Tree Updates - retrieves the structure of the portal (monitored environments). This is done by creating an XML file which portrays 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 scheduled reports and their email distribution.
  4. Active Directory Updates - CardioLog provides the ability to segment authenticated visitors by their user names and the groups they belong to. The Active Directory Updates service component retrieves the list of users and groups directly from Active Directory.
  5. User Categories Updates - CardioLog provides the ability to segment visitors by any custom category. The User Categories Updates service component retrieves the list of custom categories from a designated web service.

The Data Collection Process

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

Tracking of usage data operates in a non-invasive transparent manner and does not affect the monitored website's overall performance and response time. It is asynchronous to the monitored website’s execution and users' activity, thus has no direct impact on the monitored environment.

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


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 website pages.

CardioLog Agent File

Bytes Sent

Bytes Received


/CardioLogAgent/ca.aspx (optional)

/CardioLogAgent/caUser.aspx (optional)










The download time for the Tracking Agent JavaScript code is dependent upon multiple factors - such as 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 a connection error, in order to avoid unwanted overhead, the tracking agent tries to reconnect after 60 seconds (configurable) in order to send usage data. The page will be displayed without modifications - if any - after 5 seconds (configurable).

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


Data Collected by CardioLog Analytics

CardioLog Analytics collects data from various sources:

  1. Page tagging: page URL, query string, date and time, user ID, session ID, browser type and operating system, IP address. 
  2. Active Directory or SharePoint user profiles: user name, email, department, location etc. (configurable)
  3. Social activity from SharePoint or Yammer: ratings, likes, follows etc.
  4. Website tree service: Page ID, URL, title, content type, template, owner, editor, created, updated, size, and additional meta data fields (configurable).
Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk