Performance alert message data is used in the Autonomic Events Service (AES) Enterprise Edition application, and in the PegaRULES Log Analyzer (PAL) tool. These messages contain a set of field values that identify the alert, the conditions that caused it, and the state of the system when it occurred. Each field is separated by an asterisk. The values in these fields contain information that can help you identify and correct the issues that are triggering the alerts.
The messages are organized into versions that determine which fields appear in a message. For example, alert version 5 contains all the fields from versions 1 through 5. Alert versions do not correspond to PRPC or Pega 7 Platform versions. For example, PRPC 5.4 uses alert version 6.
The following table lists the fields as they are displayed in the header row of the Excel spreadsheet (from left to right).
The time that the alert was generated in the system, translated into GMT from the system time.
2007-11-06 06:11:55,436 GMT
The version of the header for the alert. This information is used to tell the system which “parse” rule to use to parse this message (in case different information is added to the messages in the future).
The message key for the type of alert.
The value of the key performance indicator (KPI), which triggered the alert.
The threshold value of the key performance indicator, as set in the prconfig.xml file.
The node (hash) ID in the Process Commander system.
|tenantName||The tenant name if the alert occurred on a multitenant system; otherwise, not applicable.||7||PDCDevelopment|
|tenantHash||The tenant hash if the alert occurred on a multitenant system; otherwise, not applicable.||7||7fa989de9cc4518a8e91de50e6617fee|
The hash name of the requestor.
The user ID associated with the requestor for which the alert occurred. (Only if available. Some alerts might not have a userID.)
The work pool that the user was in at the time of the alert generation, if available.
The rule application and version used at time of alert.
The hash code that identifies the requestor's ruleset list.
The flag that identifies whether the user is allowed to check out rules.
The interaction number for this interaction with the server (can be used to match this data with PAL readings or DBTrace).
|correlationID||The ID used to filter messages arriving on the request queue; by default, the requestor ID.||8||HBD0D23C033AEF266B62AAC50C393683F|
The unique number that identifies each alert in a heavily used system. To ensure uniqueness, the key definition of each alert has three parts:
Adding the unique alert number to the other two fields guarantees individuality.
The name of the thread on which the alert happened.
The name of the Pega thread on which the alert happened.
Usually, the path to a Java class file (but does not have to be). This field shows the Java class inside which the alert was generated.
An indicator in the engine process that shows the state of processing when the message occurred. (Might not be available for all alerts.)
The stream or activity that is referenced in the URL that started the interaction.
The first activity that was executed.
The last step that was executed.
|ClientPageLoadID||The total elapsed time, in milliseconds, from when the user clicks to when the screen has finished rendering.||8||23|
|Future 2||For future use.|
|Future 3||For future use.|
|Future 4||For future use.|
An internal trace of the most recent actions executed by the interaction.
A snapshot of PAL at the time of the alert.
The class of the primary page at the time of the alert.
The name of the primary page at the time of the alert.
The class of the step page at the time of the alert.
The name of the step page at the time of the alert.
The Pega stack at the time of the alert.
The clipboard page data on the parameter page at the time of the alert.
Information that is specific to this alert message is stored in a variable length string.
The number of database bytes input for this interaction has
Order of fields by alert version
The following table lists the fields in the order that they are shown in the log file for alert versions 6 through 8. Fields that were added in that version are shown in bold.
|Version 8||Version 7||Version 6|