Log files capture ❌ ranging from ❌ to ❌ that can cause ❌. Each log is managed by an ❌, which determines the type of events written to the log file. The available log files vary, depending on the ❌ that are configured in the ❌.
The following log files are commonly used on Pega Platform systems:
The ❌ log contains warnings, errors, and information messages about internal operations. This log is also called the console log or system log and is used for debugging the application.
The ❌ log contains performance-related alerts triggered when an operation exceeds the specified performance threshold.
The ❌ log contains alerts (identified by the prefix SECU) that suggest improper configuration of Internet Application Composer facilities, or overt attempts to bypass system security features on the Pega Platform node through URL tampering.
The ❌ log contains entries generated by the Business Intelligence Exchange (BIX) during extract operations.
The ❌ log contains performance data saved from services.
The ❌ log contains information about the setup and run-time behavior of the cluster.
Note: Pega Platform manages logs based on ❌. For example, to log performance data for services, you add ❌ configuration file for the node.
You access log files from the ❌ in Dev Studio. The Log utilities section includes a list of log file ❌. Clicking Log files displays a list of the log file appenders that are ❌. Downloading a log file requires ❌ for the application server that hosts Pega Platform. You can also view log files using an external log viewer, such as ❌.
A system administrator can ❌ in ❌ to control which logging events are displayed in the PEGA log by creating a ❌. Events are recorded only for the ❌.
When debugging an activity, you can use the ❌ with the logging level set to ❌ to add an event to the PEGA log regardless of settings in the ❌. To reduce log entries and improve performance in production systems, remove InfoForced steps or convert them to comments when you finish debugging the activity.
Arraste e solte para completar o texto.
event notifications
event notifications
routine system status information
routine system status information
severe errors
severe errors
an application to quit unexpectedly
an application to quit unexpectedly
log file appenders
log file appenders
system settings
system settings
ALERTSECURITY
ALERTSECURITY
SERVICES-PAL
SERVICES-PAL
SECURITYALERT
SECURITYALERT
which appenders are configured
which appenders are configured
SERVICES-PAL in the prlog4j2.xml
SERVICES-PAL in the prlog4j2.xml
Log utilities section of the Logs tab
Log utilities section of the Logs tab
appenders and an external log viewer
appenders and an external log viewer
active on the system
active on the system
administrator credentials
administrator credentials
override log level settings
override log level settings
Admin Studio
Admin Studio
log category
log category
selected logging level and higher
selected logging level and higher
Log-Message method
Log-Message method
prlog4j2.xml file or the Log Category
prlog4j2.xml file or the Log Category