Historical data not available in the database and on Agent Trace reports in MSTR

Last Updated : Dec 08, 2022 |
Historical data is not available in the database and on canned or custom Agent Trace reports in MSTR. This data is of agents who are being traced while they are logged onto Avaya Workspaces and handling calls.

Cause

Orca-trace-measure-proc is not installed during Avaya Analytics™ deployment.

Solution

  1. Log in to the Cluster Control Manager (CCM) console as the customer user.
  2. Switch to being the root user by entering the command su.
  3. Check if the processor is deployed, run the following command:
    ADDITIONAL INFORMATION: [root@ccm~]#kubectl get pods --all-namespaces | grep orca-trace-measure-proc
  4. Open deployment spreadsheet, go to Orca tab > Customize Processor to Install field. If the value of the field is set as False, then set it to True.
    1. Under Measure Processors, if the Install value for Agent Trace Measure Processor is set to False, then the Agent Trace Measure Processor is not deployed.
      ADDITIONAL INFORMATION:
      To deploy this processor, see section Preparing the deployment spreadsheet in Deploying Avaya Analytics™ for Avaya Oceana® guide.