The PEGA0011 alert is triggered when the total request time required for a service request exceeds the threshold setting.

The total request time is usually measured as the time required to process a request — from the time when the Pega 7 Platform server receives the service request from an external system until the Pega 7 Platform sends the response back to the external system or client.

Example message text

SOAP-RuleSearchPackage.Data-RuleSearch.RuleSearchService : Total request time interaction has exceeded the threshold of 1000 ms: 9072 ms

Default prconfig.xml settings

<env name="alerts/services/totalRequestTime/threshold" value="1000" />

The default threshold setting is 1000 milliseconds (1 second).

<env name="alerts/services/totalRequestTime/enabled" value="true" />

Toggles the alert to on ("true") or off ("false").

Reason for the alert

In versions prior to PRPC 5.3, if the totalRequestTime alert is triggered, it enables the following alerts that provide additional detail. Use these alerts to re-create the issue that caused the PEGA0011 alert to locate where in the service process the lengthy delay occurs.

• inboundMappingTime (PEGA0014)
• activityTime (PEGA0013)
• outboundMappingTime (PEGA0012)

For PRPC versions 5.3 and later, these alerts have been removed, and their elapsed time has been added to the PEGA0011 alert.