Table of Contents

PAL events in Pega Predictive Diagnostic Cloud

Pega Platform™ captures information about the performance of request processing in your application and stores the information in PAL timers and PAL counters. You can view PAL statistics for each event. When the processing of a browser or service request causes delays, Pega Predictive Diagnostic Cloud™ (PDC) analyzes PAL statistics from the relevant alerts and identifies possible sources of delays in request processing in your system.

The total request time is measured as the time required to process a request: from the time when a Pega Platform server receives the service request from an external system until Pega Platform sends the response to the external system or client. PAL statistics from the PEGA0001 and PEGA0011 alerts provide a reliable image of the performance of the entire request processing. PDC analyzes PAL data from these alerts, and creates a PAL event when a single interaction takes more than 30% of the total interaction time. These events can help you to identify the area of your system where you should start resolving the problem. For more information about interpreting PAL statistics, see Understanding system resources.

The following PAL events represent delays in various types of operations that are performed during an interaction:

  • Rule I/O time (PAL0001) pxRuleIOElapsed

    Rules were retrieved from the database y times, which accounted for x% of interaction time.

  • DP load time (PAL0002) pxDeclarativePageLoadElapsed

    Data pages were created or loaded y times, which accounted for x% of interaction time.

  • Other I/O time (PAL0003) pxOtherIOElapsed

    Non-rule-resolved instances from the database were accessed y times, which accounted for x% of interaction time.

  • CPU time (PAL0004) pxTotalReqCPU

    Elapsed CPU time accounted for x% of interaction time.

  • DB I/O time (PAL0005) pxRDBIOElapsed

    Database queries were executed y times, which accounted for x% of interaction time.

  • Declarative rules time (PAL0006) - pxDeclarativeRulesInvokedElapsed

    Declarative rules were executed y times, which accounted for x% of interaction time.

  • Connector rules time (PAL0007) pxConnectElapsed

    Connect rules were executed y times, which accounted for x% of interaction time.

  • Java generation time (PAL0008) pxJavaAssembleElapsed

    Java was generated y times, which accounted for x% of interaction time.

  • Java compilation time (PAL0009) pxJavaCompileElapsed

    Rules were compiled y times, which accounted for x% of interaction time.

  • Commit time (PAL0010) pxCommitElapsed

    Explicit database commit operations were performed y times, which accounted for x% of interaction time.

  • Inferring Java (PAL0011) pxInferGeneratedJavaHLElapsed

    The engine attempted to avoid rules assembly by identifying existing Java for a rule y times, which accounted for x% of interaction time.

Suggest Edit

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.