Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-10067

Ability to configure command exception logging

    XMLWordPrintable

    Details

      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

        mgm-controller-panel

        This is the controller panel for Smart Panels app

          Attachments

            Issue Links

            is related to

            Task - A task that needs to be done. CAM-10593 The process engine should only log exceptions that do not propagate to user code

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                meyer Daniel Meyer
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: