Article

Alert log message data

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).

Field Description Alert version Example

generatedDateTime

The time that the alert was generated in the system, translated into GMT from the system time.

1

2007-11-06 06:11:55,436 GMT

version

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).

1

5

msgID

The message key for the type of alert.

1

PEGA0004

kpiValue

The value of the key performance indicator (KPI), which triggered the alert.

1

50021042

kpiThreshold

The threshold value of the key performance indicator, as set in the prconfig.xml file.

1

50000000

serverID

The node (hash) ID in the Process Commander system.

1

ed3d462358e52d133
c4d805bcaf1dc40

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

requestorID

The hash name of the requestor.
If the name begins with “H”, this requestor is being used by a user (HTTP interaction)
If the name begins with “A”, this requestor is being used by an application (example: SOAP service)
If the name begins with “B”, this is a batch requestor (used by agent processing)
If the name begins with “P”, this requestor is used for portlet support

1

HA39AD8D65146D5
8B903281E806DD9DCD

userID

The user ID associated with the requestor for which the alert occurred. (Only if available. Some alerts might not have a userID.)

1

theDeveloper@pegasystems.com

workPool

The work pool that the user was in at the time of the alert generation, if available.

4

PegaAccel

ruleAppNameVersion

The rule application and version used at time of alert.

6

PegaRULES:5.4

encodeRulesetList

The hash code that identifies the requestor's ruleset list.

4

bd72de7fe35adfdfcb28b
7486a6b7a20

allowsRuleCheckOut

The flag that identifies whether the user is allowed to check out rules.

4

N

interaction

The interaction number for this interaction with the server (can be used to match this data with PAL readings or DBTrace).

2

30

correlationID The ID used to filter messages arriving on the request queue; by default, the requestor ID. 8 HBD0D23C033AEF266B62AAC50C393683F

uniqueInt

The unique number that identifies each alert in a heavily used system. To ensure uniqueness, the key definition of each alert has three parts:

  • Date/timestamp
  • Node name of the system
  • Unique alert number

Adding the unique alert number to the other two fields guarantees individuality.

1

185

threadName

The name of the thread on which the alert happened.

1

http-80-31

pegaThreadName

The name of the Pega thread on which the alert happened.

6

STANDARD

loggerName

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.

1

com.pega.pegarules.engine.
database.DatabaseImpl

stack

An indicator in the engine process that shows the state of processing when the message occurred. (Might not be available for all alerts.)

1

10.1.20.171|172.21.5.190

lastInput

The stream or activity that is referenced in the URL that started the interaction.

4

Activity=FinishAssignment

firstActivity

The first activity that was executed.

4

Rule-Obj-Activity:FinishAssignment

lastStep

The last step that was executed.

4

EMBED-LISTPARAMS GETCONTENT
#20070809T151219.534 GMT Step: 1
Circum: 0

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.

traceList

An internal trace of the most recent actions executed by the interaction.

4

441:haveAccessWithFrame
:Rule-HTML-Fragment;442:getStream Rule-HTML-Section:ShowListView;

palData

A snapshot of PAL at the time of the alert.

4

RuleCPU=0.03;RDBWithStreamCoun
t=1 ;RuleFromCacheCount=32;

primaryPegeClass

The class of the primary page at the time of the alert.

5

Embed-ListParams

primaryPageName

The name of the primary page at the time of the alert.

5

ListParamsPage

stepPageClass

The class of the step page at the time of the alert.

5

Embed-ListParams

stepPageName

The name of the step page at the time of the alert.

5

ListParamsPage

pegaStack

The Pega stack at the time of the alert.

5

java;RULE-OBJ-ACTIVITY
EMBED-LISTPARAMS GETCONTENT
#20070809T151219.534 GMT Step: 1 Circum: 0;

parameterPage

The clipboard page data on the parameter page at the time of the alert.

5

;pyMetadataRef=;ViewPrPgName=
pyWorkPage.pyMetadata;

line

Information that is specific to this alert message is stored in a variable length string.

1

The number of database bytes input for this interaction has
exceeded the "warning" level for
Requestor HA39AD8D65146D58
B903281E806DD9DCD,
operator
maqbulb@virtusa.com Maximum bytes: 50000000 Actual bytes: 50021042

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

generatedDateTime​
version
msgID​
kpiValue
kpiThreshold
serverID
tenantName
tenantHash
requestorID
userID
workPool
ruleAppNameVersion
encodeRulesetList
allowsRuleCheckOut
interaction
correlationID
uniqueID
threadName
pegaThreadName
loggerName
stack
lastInput
firstActivity
lastStep
clientPageLoadID
future 2
future 3
future 4

traceList
palData
primaryPageClass
primaryPageName
stepPageClass
stepPageName
pegaStack
parameterPage
line

generatedDateTime​
version
msgID
​kpiValue
kpiThreshold
serverID
tenantName
tenantHash

requestorID
userID
workPool
ruleAppNameVersion
encodeRulesetList
allowsRuleCheckOut
interaction
uniqueID
threadName
pegaThreadName
loggerName
stack
lastInput
firstActivity
lastStep
traceList
palData
primaryPageClass
primaryPageName
stepPageClass
stepPageName
pegaStack
parameterPage
line

generatedDateTime​
version
msgID
​kpiValue
kpiThreshold
serverID
requestorID
userID
workPool
ruleAppNameVersion
encodeRulesetList
allowsRuleCheckOut
interaction
uniqueID
threadName
pegaThreadName
loggerName
stack
lastInput
firstActivity
lastStep
traceList
palData
primaryPageClass
primaryPageName
stepPageClass
stepPageName
pegaStack
parameterPage
line

Published April 2, 2008 — Updated November 7, 2017


0% found this useful

Related Content

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.