Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Alert format

Updated on April 5, 2022

Each line of the log contains multiple fields, delimited by a single asterisk character. Each line contains the following fields. The first column of the table is the Excel column after you have imported the file into Excel.

ColumnFieldDescription
ATime stampDate and time of the alert event in UTC format.
BVersionDisplays the header version for the alert. For example, "8".
CMessage ID Identifier of alert type, for example PEGA0011.
DKPI ValueObserved duration in milliseconds or count of value, known as the key performance indicator.
EKPI ThresholdThreshold value for this alert type, in milliseconds or count.
FServerIDNode ID for the node that is the source of the alert event.
IRequestor ID Session identifier; the first letter (A, B, H, or P) identifies the requestor type.
  • A - requestor is being used by an application
  • B - batch requestor used by agent processing
  • H - requestor is being used by a user (HTTP interaction)
  • P - requestor is used for portlet support
JUser ID Operator ID of requestor, or none.
KWork pool Work pool that the requestor uses, or none.
LRule application name versionRule application and version used at the time of the alert.
MEncoded RulesetHash code identifying the requestors ruleset list.
NCheckout EnabledY indicates that the activity in the Activity field is in a personal ruleset; that a developer has checked out the activity.
OInteraction numberFor alerts from browser sessions, the interaction number (as it appears on the Performance tool display).
PCorrelation IDID used to filter messages arriving on the request queue. By default, the requestor ID.
QSequenceSequence number for this alert in the log; unique within this log.
RThreadInternal name of the PRThread instance, or NA if this alert is not from a Thread.
SPega Thread NameThe name of the Pega thread on which the alert happened.
TLoggerJava class that produced the alert instance.
UStackAn indicator in the engine process that shows the processing state when the message occurred. (Not available for all alerts.)
VLast InputFor alerts from interactive requestors, a portion of the URL received in the most recent interaction. Typically the text Stream= or Activity= and the name of an activity or stream rule run by the URL.
WFirst ActivityFor alerts from interactive requestors, the first activity or stream run by this requestor in the current interaction. (This activity or stream may or may not have caused the alert.)
XLast StepIf the First Activity field identifies an activity, this field identifies the step number last completed, when available.
YReservedReserved.
ZReservedReserved.
AAReservedReserved.
ABReservedReserved.
ACTrace ListColon-delimited string containing the most recent 50 operations of this requestor before the alert event. Each operation consists of two subfields in the format number:value:.
ADPAL dataFor some Message ID types, a set of selected of Performance tool statistics at the time of the alert. A colon delimited string in the format propertyname:value:. Values are in milliseconds, bytes, or counts.
AEPrimary page classThe class of the primary page at the time of the alert.
AFPrimary page nameThe name of the primary page at the time of the alert.
AGStep page classThe class of the step page at the time of the alert.
AHStep page nameThe name of the step page at the time of the alert.
AIPega stackThe Pega stack at the time of the alert.
AJParameter pageThe clipboard page data found on the parameter page at the time of the alert.
AKLineA text description of the alert.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us