The logs contain information about processing and interactions among identity applications components that occur while fulfilling users and administrative requests and during general system processing. By enabling the correct log levels for various packages, an administrator can monitor how identity applications process users and administrative requests.
You can change the log level of the packages individually by searching a package name. If you want to change the log level for all the packages:
Select Change log level for the listed packages.
Select the log level from the list.
Table 6-1 Types of Log Levels
|
Level |
Description |
|---|---|
|
Fatal |
The least detail. Writes fatal errors to the log. |
|
Error |
Writes errors that can cause system processing to not proceed. |
|
Warn |
Logs potential failures, but the impact on execution is minimal. Warnings indicate that you should be aware that this event is happening and might want to make a configuration change to avoid it. |
|
Info |
Logs informational messages. No execution or data impact occurred. |
|
Debug |
Includes debugging information. |
|
Trace |
The most detail. Writes tracing information (plus all of the above) to the log. |
NOTE:By default, the log level is set to Info for all the packages.
(Conditional) To retain these changes after restarting the application server, select Persist the logging changes.
Click Apply.
NOTE:The portal functionality and export or import of portal content within the User Application are discontinued from this release. If you have the packages corresponding to these features, manually remove the packages from the idmuserapp_logging.xml file.