> System > Operations > Logs menu item to access the Log Files tool. Here you can view or download the current Pega log from the server to your workstation. Each node on a PRPC system produces various logs, including these two:
PegaRULES-YYYY-MMM-DD.log, where the date portion of the name indicates the date the application server was recently started (on the current node).Select the > System > Operations > Logs menu item to access the Log Files tool. Here you can view or download the current Pega log from the server to your workstation.
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.
In an activity, use the Log-Message method to add a message to the Pega log.
A standalone Web application, the PegaRULES Log Analyzer (PLA) can summarize console logs. See PDN articles Understanding the PegaRULES Log Analyzer and How to use the PegaRULES Log Analyzer.
The prlogging.xml file contains settings that can cause the system to create a new Pega log daily or on a periodic basis, rather than only at startup. Consult the Administration and Security 5.3 publication for instructions.
If two or more PRPC servers are installed in a single application server instance, they write lines to a common Pega log file. If this is not desirable, you can change the name or path of the Pega log for a node by modifying the prlogging.xml file. In this example the log file name starts with PEGABLUE:
<param name="FileNamePattern"
value="C:\LOGS\PEGABLUE-'yyyy-MMM-dd'.log" />
Related terms