LinkedIn
Copied!

PEGA0058 alert: Interaction History read time above threshold

The PEGA0058 alert is triggered when the Interaction History read time exceeds its threshold for a customer record or any other entity that is associated with a decision. The increased Interaction History read time affects the latency of the decision data.

Example message text

Reading the interaction history fact record(s) took more than the threshold of <threshold> ms : <actual value> ms : SQL :<sql name>

The following variables are in the message text:

  • <threshold> is the maximum value for Interaction History read activity. The default value in milliseconds is 1000. The threshold value is set in the alerts/interactionHistoryReadTimeThreshold Dynamic System Settings.
  • <actual value> is the time, in milliseconds, that the system needed to read the Interaction History.
  • <sql name> is the database record name for which the alert has been triggered.

Reason for the alert

The Interaction History read time exceeds its threshold for a customer record or any other entity that is associated with a decision.

Next steps

To eliminate this alert:

  • Narrow down the Interaction History retrieval criteria in the strategy.
  • Review the performance of the database that is associated with the strategy.

Narrowing down the Interaction History retrieval criteria

Review the Interaction History records for a particular entity and narrow down the data retrieval criteria in the strategy.

  1. Review the Interaction History records that were retrieved for a particular entity:
    1. In Designer Studio, access the App Explorer menu.
    2. In the App Explorer menu, open the Data-Decision-IH-Fact data table.
    3. Review the data table to find out whether the amount of data retrieved for a particular entity exceeds the limit.
      Interaction History fact table
  2. Narrow down the Interaction History data retrieval criteria in the strategy:
    1. In Designer Studio, open the strategy with the Interaction History shape that triggered the alert.
    2. Double-click the Interaction History shape.
    3. On the Interaction history tab, modify the Interaction History data retrieval conditions.
      Interaction History properties

Reviewing the performance of a database

Review the performance of the database that is associated with the strategy. If the performance analyzer tool indicates that the latency of the database is high, it might point to an issue with the database.

  1. In Designer Studio, access the strategy that triggered the alert.
  2. At the bottom of the strategy canvas, click Performance to access the performance analyzer tool.
  3. Use the available analysis tools (for example, DB Trace) to analyze the latency of the database.

100% found this useful


Related Content

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.