About the Log Files tool |
Select> System > Tools > Logs > Log Filesto view or download the current Pega log, Security log, Alert log or other logs on the server node you are accessing.
Which logs appear depend on the contents of the prlogging.xml file for this node. You may see the following:
Click a file name to view one of the logs. Typically the date portion of the file name indicates that this file contains only log
The initial display shows only lines of the log for your own Operator ID (for all your sessions on this node), in pages of 25 lines each. Click a number at the bottom of the display to see the corresponding page, or next to see the next group.
Click the Options link to view or set log filtering criteria. Click Apply to review the log again with updated criteria, or Back to return to the initial window with no changes.
Field |
Description |
Lines per page |
Enter an integer between 1 and 200. |
Number of pages presented |
Set a maximum number of pages to present as numbered links, between 2 and 20. |
Filter |
Optional. Enter a text string to limit the display to only 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 either of the text links to download a log as a text file (with txt
as the file type).
Click the zip links to download a log as a ZIP file.
Application server authentication may be required. Access is controlled by the PegaDiagnosticUser
role in the web.xml
file for the DiagnosticData
servlet. Consult the Installation Guide for more information and instructions.
By default, to reduce the demand on system resources, the system first writes log output to a memory buffer that is 8 kilobytes in size. As a result, the contents on the disk log file may not yet contain output written minutes ago or even in some cases hours ago, depending on volume.
Alert log, Pega log | |
Understanding alerts |