|
Select 
> My AlertsBYRNB 2/16/10 to view lines from the current
Alert log on the server node produced by your own requestor session. (You
can access the same display from the My Alerts link of the Performance
tool summary display.) Proj-505 CODE-271
During your requestor session, a pop-up message appears briefly when an alert is triggered.
Each alert in the STANDARD Thread increments a counter
(
) located on the left side of the portal title bar. The
counter does not appear until the first alert. Alerts in the
DEVELOPER Thread or other Threads are not included in this
count, as they are unlikely to occur for users of the application you are
building, and so are not relevant to your application's runtime
performance.
Click the counter to open the list of alerts described below. When you log off and back on again, the counter resets to "0" and no counter displays.
To turn off the pop-up feature, select Preferences > View byrnb 2/16/10 from the Designer Studio Profile menu and clear the Show Alerts Popup checkbox in the My Alerts group.
This display is limited to the current Alert log;
alerts in older logs are not visible. Depending on your log file systems
settings, a new log may start each time a node is started, at specific
time each day, or on another basis.
Field |
Description |
|
The alerts are ordered by date and time; the first row is the
most current.v5.5 Click to see |
| Date and Time |
Date and time of the alert, converted from GMT to the time zone of the server. |
| Alert Type |
A text description of the alert type. For example, the text
|
| Value |
The measured value of the Key Performance Indicator, recorded in seconds, as a count, or in bytes. |
| Interaction |
The sequence number of the browser-to-server interaction since the requestor session began, as indicated by the Performance tool display. |
| Workpool |
Work pool that the requestor is using, or |
| Last Input |
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. PROJ-505 VAGUE |
| First Activity |
For alerts from interactive requestors, the first activity or stream run by this requestor in the current interaction. PROJ-505 (This activity or stream may or may not have caused the alert.)C-2658 |
If more than 20 alerts meet the criteria, the oldest 20 appear.
Field |
Description |
| Lines per page |
Enter an integer between 1 and 200 to change the number presented per page. |
| Number of pages presented |
Set a maximum number of pages to present as numbered links, between 2 and 20. |
| Filter by |
Optional. Enter a text string to limit the display to only alert lines containing an exact match anywhere within the line. Leave blank for no filtering. Case is not significant. For example, enter [email protected] to find lines containing this value, or containing [email protected]. B-19266 |
|
Alert log, key performance indicator |
|
Understanding
alerts How to monitor interactive response times. |
Working with the My Alerts display
to hide details. For an explanation of the most useful
details, see 
Alert Log 5.4, a PDF document available on the
Pega Developer Network.
Tools, accelerators, and wizards