PPM gel:log logger messages in standard logs appear as ERROR regardless of LEVEL
Article ID: 189693
Clarity PPM On PremiseClarity PPM SaaS
Since PPM 15.3 the logging mechanism for processes logs all calls to <gel:log> as error in the log files, regardless of the log-level provided. Gel log with INFO or WARN tag is not supposed to print as an error to the BG-CA log files
Logger message in the log file can have all levels.
DEBUG ERROR FATAL INFO WARN
STEPS TO REPRODUCE: Step 1: Open the PPM log configuration page (PPM_URL/niku/nu#action:security.logs) or log configuration section via CSA , set the priority level of the "com.niku.bpm" category to "ALL" and leave the Process Engine Persistence Level on the default "ERROR"
Step 2: Create a process with the following gel script which runs as a custom step in the process.
Begin Error Information: Step Action Id: 5028002 Process Instance Id: 5009006 Step Instance Id: 5005014 Error Code: bpm.raw.message Exception Trace: [Employee Data]INFO INFO INFO End Error Information
Begin Error Information: Step Action Id: 5028002 Process Instance Id: 5009006 Step Instance Id: 5005014 Error Code: bpm.raw.message Exception Trace: [Employee Data]WARN WARN WARN End Error Information
Release : 15.8 and lower releases
Component : CA PPM APPLICATION
Reported to Broadcom engineering via Defect DE54704. The defect will be reviewed for possible inclusion in a future version, service pack or patch.
There is no real workaround to parse the logger messages in the log files. Customers using log collector systems e.g. fluentd and logstash will need to consider these exceptions when parsing and collecting entries from the log files.
For more information on gel:log logging messages please visit TECHDOCS