Table of Contents

Lengthy service operations


Only available versions of this content are shown in the dropdown

Pega Platform adds a PEGA0011 alert to the Alert log when a service operation or parse rule operation takes an unusually long time. The line identifies the requestor, the service, and the value of the performance statistic. View these alerts so that you can take action to improve system performance.

Statistics available

Five elapsed time statistics are available for most service types. When any of these five measured times exceeds a corresponding threshold, the system adds a PEGA0011 alert to the Alert log.

  • pxTotalReqTime – Total request time, alerts appear by default for times exceeding 1 second.
  • pxServiceImpMapReqTime – Request mapping.
  • pxServiceOutMapReqTime – Response mapping.
  • pxServiceActivityTime – Service activity execution.
  • pxServiceParseRuleTime – Parse XML rule, Parse Delimited rule, and Parse Structured rule execution.

Three of the five statistics are available for listeners:

  • pxServiceActivityTime
  • pxServiceImpMapReqTime
  • pxServiceParseRuleTime

One of these values appears as the KPI Value in the alert message, the actual value in milliseconds that exceeded the threshold value.

Each PEGA0011 alert includes actual values for all five statistics, in the PAL Statistics field. Consult Performance tool — Statistics for services for definitions of these values. See the Pega Community article PEGA0011 alert: Total request time exceeds limit.

The statistics for pxServiceImpMapReqTime, pxServiceOutMapReqTime, pxServiceActivityTime, and pxServiceParseRuleTime are included in PEGA0011. If you want to monitor the time thresholds individually, change the enabled setting to "true". Edit the default threshold value if necessary.

  • For information about alerts and services, see the Pega Community article Testing Services and Connectors.
  • For information on all prconfig.xml file settings, see the Pega Community article Configuration Settings Reference.
  • BPEL services operate asynchronously and are not monitored by this facility. The rule type Rule-Service-BPEL is deprecated. Use Service SOAP rules instead.

Have a question? Get answers now.

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