PPM gel:log logger messages in standard logs appear as ERROR regardless of LEVEL

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

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.

<gel:script
  xmlns:gel="jelly:com.niku.union.gel.GELTagLibrary">
    <gel:log level="INFO" category="Employee Data" message="INFO INFO INFO"/>
 <gel:log level="WARN" category="Employee Data" message="WARN WARN WARN"/>
</gel:script>

Step 3. From the PPM Home organizer page > available processes section > search and run the custom process.


Expected results:
The gel-log related messages in the standard log file should log as INFO messages when gel:log level is INFO;  and warning messages when level is WARN.


Actual results:
The gel-log was logged into the log files as ERROR, when the log level of the message clearly is INFO and WARN.

BG log excerpt:

...[Custom script execution pool-64-thread-5] utilities.BpmErrors (clarity:admin:5549231__155B1265-D4B2-486C-A773-018BF1B01C45:none) 

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

Environment

Release : 15.8 and lower releases

Component : CA PPM APPLICATION

Cause

Reported to Broadcom engineering via Defect DE54704. The defect will be reviewed for possible inclusion in a future version, service pack or patch.

Resolution

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.

Additional Information

For more information on gel:log logging messages please visit TECHDOCS