System Requirements

To ensure optimal operation, it is recommended to install the CardioLog application on dedicated server and the CardioLog database on a dedicated SQL Server instance***.

The installer prerequisites can be found here.

View the following to assure that your system meets the minimum hardware and software requirements:

*   This refers to hardware allocated for the CardioLog application pool and services, not for the CardioLog SQL server

**  Up to 2,000,000 page views per month

*** The CardioLog 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 above hardware and software requirements. 
When hosting CardioLog Analytics on Microsoft Azure virtual machines (IaaS) and tracking a SharePoint on-premise farm, a site-to-site VPN is required.

The amount of resources needed for the CardioLog Scheduling Service nightly processing depends on -

• Number of websites
• Website size
• Number of scheduled reports
• The timeframe for the reports (reports for 365 days demand more resources then reports for 30 days)
• The number of events (traffic) coming in from the portal at the time of report processing

Importing large websites consisting of millions of items, user information for hundreds of thousands users, and generating hundreds of daily reports will consume most of the CardioLog application server resources. The more resources allocated, the better.

Database Sizing

Hard disk allocation depends on the size of the monitored environment and the level of activity taking place in the portal. Additional factors that should be considered are the backup and clean-up policies and the amount of data accumulated over time. For example, an installation with 10 million usage events per month requires a total disk space of maximum 600 GB for a single year of data.

In practice, the estimated database size depends on the size of the CardioLog event tables. The following formula depicts the sizing calculation for the database:

Sd = Srd × Nu × (Ns + Nsr + (Ne × 2)) × P

Where:

Sd = estimated size of the database

Srd = average size of data per event (5 KB)

Nu = number of users in the monitored environment

Ns = average number of search operations per day per user (each search operation generates 1 event)

Nsr = average number of search results clicks per day per user (each search results click generates 1 event)

Ne = average number of non-search operations (views, duration) per day per user (each non-search operation generates 2 events by default)

P = length of the monitoring period – in days