You can view the current Alert log on the server node produced by your own requestor session by using the My Alerts display. Select Issues from the Dev Studio developer toolbar.
The following summary information is displayed for each alert:
- 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
BrowserInteractioncorresponds to alert type PEGA0001, interaction times. Other types are
- 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.
- Work Pool – 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.
- First Activity – For 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.)
The alerts are ordered by date and time; the first row is the most current. Click the arrow in the first column to expand the row to view more details about the alert.
By default, 20 alerts are displayed on the page.
- Click a numbered link, next>, or <previous to scroll back and forth through the list.
- Click This Session Only to limit the display to alerts produced by your current requestor session.
- Click All My Sessions to include alerts from the current session and other sessions with your current Operator ID.
- Click Performance or Security to toggle the display between security-related alerts (SECnnnn) and performance-related events (PEGAnnnn).
- Click the Options link to view or set log filtering criteria.
You can set the following options:
- Lines per page – Enter the number of alerts to display on a page. The valid values are 1 through 200.
- 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].
- Click Apply to update the display with the new filter criteria.
- Parsing the alert log
You can import the alert log into Microsoft Excel for viewing, searching, sorting, or other analysis using the Text Import Wizard in Microsoft Excel. Fields in the alert log are delimited by an asterisk.
- Suppressing sensitive data in alerts
The alert log identifies the names of activities and other rules that have been executed. By default, PEGA0002 to PEGA0007 alerts also show parameter values and SQL statements containing property values. You can include the suppressInserts and includeParameterPage keywords in the prconfig.xml file so that parameter values and other potentially sensitive data values are omitted in prepared statement inserts:
- Summarizing the alert log
You can parse, consolidate, and summarize alert logs using the PegaRULES Log Analyzer or services such as Elastic Stack.
You can view or download the current alert log to see important notifications about the functioning of your system.
- Alert format
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.