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