[CAM-10067] Ability to configure command exception logging Created: 02/Apr/19  Updated: 02/Aug/19  Resolved: 28/Jun/19

Status: Closed
Project: camunda BPM
Component/s: engine
Affects Version/s: None
Fix Version/s: 7.12.0, 7.11.2, 7.12.0-alpha2

Type: Task Priority: L3 - Default
Reporter: Daniel Meyer Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: EasyPick, SUPPORT
Remaining Estimate: 0 minutes
Time Spent: Not Specified
Original Estimate: 0 minutes

Issue Links:
Depedendency
Related
is related to CAM-10593 The process engine should only log ex... Closed

 Description   

Currently, Camunda is very verbose logging thrown Exceptions on ERROR level, regardless of how the exception is handled by the application.

In CommandContext#close for instance, all Exceptions (except three dedicated types, defined in shouldLogFine and shouldLogInfo) are logged on ERROR level.

Proposed addition: User can control logging of command exceptions in the following way:

  • enable / disabling exception logging for commands executed from application threads
  • enable / disable execption logging for jobs that fail but still have retries left

Defaults should remain unchainged

Note:
could be engine configurations but could probably also be defining specific logger categories so that user can configure using regular logging mechanisms


Generated at Mon Oct 21 12:15:35 CEST 2019 using JIRA 6.4.6#64021-sha1:33e5b454af4594f54560ac233c30a6e00459507e.