VISUAL BASIC

Detailed explanation-1: -The PEGA log contains warnings, errors, and information messages about internal operations. This file, also referred to as the Console log or System log, is used for debugging the application. By default, the PEGA log is filtered to entries that match the current operator ID.

Detailed explanation-2: -Use the Log-Message method to append a message to the Pega log when the step is reached. Depending on method parameters and the current logging level, a line is added to the Pega log on the current node. Additions to the Pega log consume system resources. Select the LoggingLevel parameter carefully.

Detailed explanation-3: -The Alert log file is usually named PegaRULES-Alert-YYYY-MMM-DD. log . The similar Security Alert log is named PegaRULES-AlertSecurity-YYYY-MM-DD. log .

Detailed explanation-4: -The Pega Log-also known as the console log or system log-contains messages created since the server was most recently started. The log file is usually named 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).

Detailed explanation-5: -The log message level for a particular message is determined by your code. The logging level that is set in the Logging Level Settings tool determines which messages are written to the log file. Access the Logging Level Settings tool by clicking Designer Studio > System > Operations > Logs > Logging level settings.

Detailed explanation-6: -WARN – Indicates situations that might have an adverse performance implication. DEBUG – Indicates informational events useful for debugging. ALL – Indicates that all messages are logged.

Detailed explanation-7: -Check the log files for error messages. Examine errlog. log first. If indicated, check optional log files for error messages. Identify the errors associated with your problem. 14-Mar-2023