This instruction applies to the Live Monitor version included in the EPiServer 7.5 download package. The latest version (7.5+) of Live Monitor is an add-on which can be installed and upgraded from the EPiServer NuGet feed.
This document describes how to configure Live Monitor in EPiServer CMS. Live Monitor is a module for EPiServer CMS that visualizes the current traffic on an EPiServer CMS-based website, and can be used for monitoring the traffic to your website and following the behavior of visitors.
Live Monitor can be used as-is, directly from the installation with EPiServer CMS, though it is possible to change some of the default settings if required. In this document the various configuration options are described in more detail. Live Monitor is installed on the system through the (msi) installation file and deployed to a site through Deployment Center.
Note if your solution is set up in a load balancing environment, see the interval-based updates section for more information.
Template changes required for using Live Monitor
A special placeholders for the tracking scripts need to be added to the sites master page if site templates do not render required client resources for default areas Header and Footer. One placeholder should be placed inside the <head> tag and another one before the closing </body> tag. If Live Monitor is installed on ASP.NET MVC site a special HTML helpers should be used:
Refer to the Client resource management section in the EPiServer CMS SDK.
It is possible to override default client behavior by changing init parameters on the client control (these changes should be made in the SilverlightApplication.ascx file). These are:
traceservice – address to the trace service.
visitorservice –address to the visitor service.
rememberlayout (false) – if the client should remember the previously expanded nodes and on which positions they were at.
preloadDepth (3) – by default the client automatically loads nodes thee levels down, increasing this value can have a negative impact on the client performance. The rest of the nodes will be loaded on demand. Visitors that are on nodes that have not been loaded are not shown in the client.
TraceService.svc & VisitorService.svc – Services providing the silverlight client application with visitor and page data.
Default.aspx – sample web page for showing the EPiTrace client application in a browser.
Manual database setup
Run epitraceHits.sql in your EPiServer database. This will create the table epitraceHits and the stored procedures epitraceRegisterVisit and epitraceMaintenance.
Scheduled database job
The stored procedure epitraceMaintenance needs to be setup to run at least every 24 hours. The stored procedure removes information about old visits rebuilds indexes on the epitraceHits table.
Interval based updates (load balanced environments)
Live Monitor can be set up to handle client updates in two different ways. The default setup pushes visitor updates to the listening Live Monitor Silverlight clients as soon as a visit is recorded by the visitor handler. This setup requires that the visitor logging handler resides in the same web application as the visitor service, since these updates are done with direct communication between the logging handler and the visitor service.
The second setup pushes updates at a configurable interval to the clients. When a visitor views a page the visit is recorded to database by the visitor logging handler, but the visitor service is not notified. The visitor service is instead setup to load visits from the database at a configurable interval and push to the listening Live Monitor clients. This setup does not require that the visitor service and the logging handler reside in the same web application.
Interval based visitor updates must be configured in web.config. This requires that a configuration section is registered in web.config.
Further information on the configuration properties:
usePolling - turns on the interval based updates
pollingInterval - determines the number of seconds between client updates
Using Live Monitor on websites with multiple site bindings
Live Monitor relies on WCF services for communication between the Silverlight client and the web server. If you are using multiple site bindings (for example, http://mysite.com and http://www.mysite.com) on your site, there is some specific configuration required.
If your site is running on ASP.NET 4 or later you can enable multiple site bindings using a configuration setting specific for this purpose. This configuration setting is a requirement if you want to run Live Monitor on multiple sites in an EPiServer Enterprise setup with multiple bindings.
If your site are running ASP.NET 3.5 you will need to select one specific address where Live Monitor should be available by configuring the “base address prefix filters”.
<configuration><system.serviceModel><serviceHostingEnvironment ...><baseAddressPrefixFilters><!-- this is the address from which I want to run
the live monitor client --><addprefix="http://mysite.com"></baseAddressPrefixFilters></serviceHostingEnvironment></system.serviceModel></configuration>
Using Live Monitor on websites through HTTPS scheme
Open web.config and set bindingConfiguration of the TraceService endpoint to a binding with the security mode set to “transport” as shown in the following example:
Some machines may need registering a MIME type for extension .xap as application/x-silverlight-app. IIS7, update web.config. IIS5–IIS6: Go to IIS Manager > Server > Properties > Mime Types > New > Extension > .XAP MIME type: application/x-silverlight.