CA RiskMinder Release Notes › New Features › Logging Enhancements

Logging Enhancements

The following are the logging enhancements in this release:

• The Master Administrator can now change log levels without restarting the RiskMinder Server and Case Management Server.
• RiskMinder Java SDK now logs additional information for easy correlation with the RiskMinder Server log files.
• RiskMinder now logs information in a concise manner at the INFO level to gather sufficient information about a transaction.
• New Startup Log Files:

  Because RiskMinder comprises two server modules, RiskMinder Server and Case Management Queuing Server, two new startup log files have been introduced:

  • arcotriskfortstartup.log: When you start the RiskMinder Server, it records all startup (or boot) actions in this file. The information in this file is very useful in identifying the source of the problems if the RiskMinder service does not start up.
  • arcotriskfortcasemgmtstartup.log: When you start the RiskMinder Case Management Queuing Server, it records all startup (or boot) actions in this file. The information in this file is very useful in identifying the source of the problems if the Case Management Queuing service does not start up.
• For all organizations, RiskMinder Server now logs active Rulesets and parameters of all the rules belonging to a particular Ruleset during server startup and refresh.
• Logging at the DETAIL level has been reduced significantly to reduce disk space requirements in case the servers need to be run at the DETAIL logging level.
• A new log level called Trace has been added in RiskMinder Server and Case Management Queuing Server components.

  This log level is useful in production systems to gather vital information to investigate complex issues.

• RiskMinder Server now performs audit logging after a response is returned.
• Logging has been enhanced on the Case Management page to help with database query performance tuning.