C-2383 DORID Each node on a Process Commander system produces two logs:
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> System > Tools > Logs > Log FilesBYRNB 2/25/10 to view or download the current Pega log from the server to your workstation. BUG-2457 date
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. SR-7761
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 PRKB-25406 Understanding the PegaRULES Log Analyzer and PRKB-25392 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. SR-1102 SR-7252 SR-7291
SR-1140
If two or more Process Commander 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: SR-3264
<param name="FileNamePattern"
value="C:\LOGS\PEGABLUE-'yyyy-MMM-dd'.log" />
alert log, appender, PegaRULES Log Analyzer, prlogging.xml file | |
About
the Logging Level tool
About the Log Files tool Log-Message method |