|
Use this tool to support debugging by
temporarily overriding the severity settings in the
prlogging.xml file for the current node.
For example, you can change the logging level for activities
in the Work- class from FATAL to
DEBUG. Thereafter, Olog() calls in Java steps that
have a severity setting of DEBUG or lower appear
in the Pega log.
The changes you make take effect immediately and remain in force until the server on the node is stopped, or until you or another developer use this tool again to reset them.
The prlogging.xml file is not altered. Logging
on nodes other than your current node is unaffected.
Field |
Description |
|
Logger Name
|
Use SmartPrompt to list all Java classes in
|
| Current Level |
After you click Get Current Level , this field contains the current logging level for the class in the Logger Name field. |
| Set Level |
Through the Log-Message method or Java oLog() calls, your code determines the severity of each message. |
| Get Current Level |
Click to retrieve and display the current logging level for the logger in the Logger Name field. |
| Set Level |
Click to apply the level in the Set Level field to the class in the Logger Name field. |
| Clear |
Click to erase input on the form. |
| Reset All |
Click to remove all changes made with this tool by you
or others. Logging for the current node reverts to the
original settings in the |
|
log4j, prlogging.xml file |
|
Log-Message method |
Help —
Logging Level Settings tool
Identify a Java class or other
logger category to be logged.
RuleSets and the
Process Commander class hierarchy are not relevant to
logging. If you set logging events for an activity named
Data-Party.Research and your system includes several
activities of that name (in various RuleSets and
versions), executions on the current node of any
of these activities may produce logged events.
Tools, accelerators, and wizards