Skip to main content

Changing the parameters for monitoring lengthy services

Suggest edit Updated on May 11, 2022

You can change the parameters that the system uses to monitor long-running services. For example, if your alert log shows excessive PEGA0011 alerts which you have already debugged and have determined that they need not be logged, you can change the logging parameters.

The default prconfig.xml settings for these alerts are as follows:

     <env name="alerts/services/totalRequestTime/enabled" value="true">
     <env name="alerts/services/totalRequestTime/threshold" "1000">
     <env name="alerts/services/inboundMapping/enabled" value="false">
     <env name="alerts/services/inboundMapping/threshold" "500">
     <env name="alerts/services/outboundMapping/enabled" value="false">
     <env name="alerts/services/outboundMapping/threshold" value="500">
     <env name="alerts/services/activityTime/enabled" value="false">
     <env name="alerts/services/activityTime/threshold" value="500">
     <env name="alerts/parse/totalTime/enabled" value="false">
     <env name="alerts/parse/totalTime/threshold" value="500">
  1. Optional: For the value you want to change, update the prconfig.xml file to specify whether the alert should appear in the log and the time threshold for the alert in milliseconds.For example: To set a minimum value for the totalRequestTime element in milliseconds to 850 and to control whether pxTotalReqTime alerts appear, add these elements to the prconfig.xml file:
         <env name="alerts/services/totalRequestTime/enabled" value="true">
         <env name="alerts/services/totalRequestTime/threshold" value="850">
    1. Stop and redeploy or restart the Pega Platform server.
  2. Optional: As an alternative to updating the prconfig.xml file, you can use dynamic system settings to configure your application. See Configuring dynamic system settings.
  3. Monitor the Alert log for messages.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us