Configuring logging levels on an application server
There are times where it is necessary to obtain more information for troubleshooting than the default level of logging generated by the product, but that generates large logs. To avoid logs that are overwhelmingly large, it is recommended to only activate additional logging for the binaries under investigation.
There are two methods to adjust the logging level covered below; from the command line interface (CLI) using psdebug or configuring the Logging service (idmlogsvc) using the WebUI (web-based user interface). These methods both assume the issue is occurring on the Bravura Security Fabric server, rather than other systems .
The general workflow for generating the additional logging is as follows:
Precisely define the required steps to reproduce the issue.
Make note of the time and rotate the logs to generate clean logs if necessary:
<instance>\instance.bat
<instance>\samples\idmlib\script\rotate_logs.py
OR
<instance>\idmlogsvc.exe -rotatelog
Set the desired log level, from the command line or from the web interface .
Reproduce the issue by following the previously defined steps.
Reset to the default log level.
Verify log output.
Provide context for the debug logging data:
The date/time of the workflow/process
Step-by-step details of the workflow/process that can be followed to reproduce the issue
Any relevant values to look for (userids, attributes or PDR involved)
A zip archive of
idmsuite.logand any input/output KVG files
Make use of the information.
Configuration of both psdebug and idmlogsvc is server-specific. Their settings are saved in the Windows registry in keys which are excluded from file replication .
Using either of these methods results in increasing the log level for the duration of the time required to reproduce a problem in order to help troubleshoot an issue or monitor for specific log entries not available at Default (Info) level.