Changing the parameters for monitoring lengthy services
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">
- 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.- Stop and redeploy or restart the Pega Platform server.
- Optional: As an alternative to updating the
prconfig.xml
file, you can use dynamic system settings to configure your application. See Using dynamic system settings. - Monitor the Alert log for messages.
Previous topic Lengthy service operations Next topic Verifying that an instance is running