Gravatar for praful.memane@towerswatson.com

Question by prafulmemane, Nov 19, 2015 6:34 PM

Configuring coveo for indexing sitecore_analytics_index

Hi, Currently, we have an OOTB Index - SitecoreAnalyticsIndex (Lucene) which contains all the Analytics data indexed for reporting purpose.

We need to configure our sitecore CM Server and Processing Server such that we can use the Coveo for indexing our Analytics data instead of Lucene.

I have read all that is in this link ( https://developers.coveo.com/display/public/SC201505/Understanding+the+Analytics+Index+and+xDB ) and have a few questions :

  1. Where does the index information for sitecoreanalyticsindex needs to be added (Sitecore.ContentSearch.Analytics.config or Sitecore.ContentSearch.Lucene.Index.Analytics.config ?
  2. How do we configure the Processing Website installation to use the coveo index for adding/updating/deleting analytics data ?
  3. How does the CMS (reporting feature) read from the sitecoreanalyticsindex (coveo) and not lucene?
Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Nov 20, 2015 12:07 PM

Hi,

Before getting too technical with my answer, I first want to know what are your motivations to convert the SitecoreAnalyticsIndex from Lucene to Coveo?

From my experience, there's no gain to do so because the Coveo UI components don't use the analytics index. In fact, it can negatively affect the other Coveo indexes because of the big indexing and querying load that the analytics index will add to Coveo Enterprise Search. Keeping the analytics index as a Lucene one will ensure quick indexing and querying of the other (Core, Master and Web) Coveo indexes and a great visitor experience.

Gravatar for praful.memane@towerswatson.com

Comment by prafulmemane, Nov 20, 2015 3:01 PM

So the answer as to why we want to use coveo is because of the way our architecture is setup link text. We have a separate processing website which takes care of the aggregation of analytics data. The setup needs to have an external index (vis-a-vis lucence (folder) index) so that it can be accessed between the Processing and CMS Websites (Reporting feature) Sitecore recommends using SOLR but since we are already using Coveo and don't want to invest in a separate search engine for just one index.

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Nov 20, 2015 3:05 PM

That's a good motivation. Depending on the additional number of indexed documents and queries generated by the analytics index, you may have to upgrade the Coveo servers hardware or add Coveo mirrors to keep a great performance level.

For this reason, we do not recommend using Coveo for the Sitecore Analytics index.

1 Reply
Gravatar for jflheureux@coveo.com

Answer by Jean-François L'Heureux, Nov 20, 2015 12:07 PM

It is not recommended to use Coveo for the Sitecore Analytics index because it will decrease the performance of your other Coveo indexes used to deliver a great search experience to your end users. We recommend using Lucene or SOLR for the Analytics index.

To answer your questions:

  1. There used to be a separate Coveo.SearchProvider.Analytics.config file. This file was never included in Coveo for Sitecore out of the box. Customers needed to contact us to get it. This file is not available anymore.
  2. I'm not an expert in Sitecore analytics. I don't know this answer.
  3. A Coveo index with the id attribute the same as a Lucene index is registered in Sitecore before the Lucene one declared in a file that is alphabetically later. The Lucene one won't be registered in Sitecore because an index with the same id is already registered. Thus, Sitecore will use the Coveo index instead of the Lucene index.
Gravatar for praful.memane@towerswatson.com

Comment by prafulmemane, Nov 20, 2015 3:00 PM

Thanks for your response, and please suggest who do we contact for the file (config).

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Nov 20, 2015 3:06 PM

You can contact sitecore@coveo.com by linking to this discussion thread for context.

Thank you,

Jeff

Ask a question