Discovery Accelerator Analytics failure in one Case can stop Analytics data collection in other Cases

book

Article ID: 100012163

calendar_today

Updated On:

Description

How to configure the automatic pausing of analytics data collection

You can customize the new functionality by setting configuration values in the AnalyticsServerApp.exe.config file. This file is in the Discovery Accelerator installation folder, which is typically C:\Program Files (x86)\Enterprise Vault Business Accelerator.

The available configuration values are as follows:



  • Turns the auto-pause functionality on ("true") or off ("false").
     


  • Specifies the frequency in seconds with which Discovery Accelerator should check for failures of analytics tasks.
     


  • Specifies the number of times that an analytics task must fail before Discovery Accelerator pauses the collection of analytics data in the associated case.

If you change any configuration value, you must restart the Enterprise Vault Accelerator Manager service to put the change into effect.

 

 

Resolution

This issue has been fixed in Discovery Accelerator 11.0.

At regular intervals (the default is 45 seconds), Discovery Accelerator 11.0 checks for any analytics tasks that have failed more than five times. If Discovery Accelerator finds such a task, it automatically pauses the collection of analytics data in the associated case and displays the following message in the Analytics tab of the Discovery Accelerator client:

Automatically paused analytics because of the repeated failure of an internal task. Contact Technical Support.

In addition, Discovery Accelerator records the following event in the event log:

APP Analytics - Task Controller has paused analytics on the following case because of the repeated failure of an internal task:
CaseID: nn (Customer: Customer_Name)
Contact Technical Support.

Discovery Accelerator then proceeds with analytics data collection in the other cases.

Issue/Introduction

If you enable analytics in several cases at once, an error in data collection or rule processing in one case can prevent these activities from completing in all the other cases. The presence of the following events in the event log on the Discovery Accelerator server is usually an indication of this issue.
IDDescription
421APP AS - CustomerID: # - An error has occurred when getting ingestion error count.
497APP Analytics - AnalyticsIngesterTask.exe with TransactionID nnn encountered an unexpected error, terminating.
503APP Analytics - Add Items Task with TransactionID nnn Failed.
519APP Analytics - AnalyticsConversationAnalyzerTask.exe (PID = nnn) with TransactionID nnn failed to read items to process, terminating.
 

Additional Information

ETrack: 2966474