Logging Level Settings tool |
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 display in the 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.
com.pega.pegarules
, or enter a category. Examples:Rule-Obj-Activity
to review or update the logging level for all activity executionsRule-Obj-Activity.<activity name>
to update the logging level for all activities with a given name in any Applies To class.com.pega.pegarules.engine.context.Agent
to update the level for all agentsNote: RuleSets and the Pega 7 Platform 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.
OFF
to be included:ALL
— Same as DEBUG
DEBUG
— Least severeWARN
ALERT
ERROR
FATAL
— Most severeOFF
— No messages loggedThrough the Log-Message method or Java oLog() calls, your code determines the severity of each message.
prlogging.xml
file.