Currently, the stacktrace is logged on level ERROR, i.e. it is always logged. In the context of CAM-10593 and that the stacktrace is rather a tool for debugging than for error reporting, it makes sense to log it on level DEBUG.

        This is the controller panel for Smart Panels app

            [CAM-10627] Log BPMN stack trace on level DEBUG

            Thorben Lindhauer created issue -
            Thorben Lindhauer made changes -
            Link New: This issue is related to CAM-10593 [ CAM-10593 ]
            Thorben Lindhauer made changes -
            Fix Version/s New: 7.12.0 [ 15387 ]
            Fix Version/s Original: 7.11.0 [ 15343 ]
            Thorben Lindhauer made changes -
            Remote Link New: This issue links to "Page (camunda confluence)" [ 13039 ]
            Yana Vasileva made changes -
            Assignee New: Yana Vasileva [ yana.vasileva ]
            Yana Vasileva made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Yana Vasileva made changes -
            Assignee Original: Yana Vasileva [ yana.vasileva ] New: Tobias Metzke-Bernstein [ tobias.metzke ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            Remaining Estimate New: 0 minutes [ 0 ]
            Original Estimate New: 0 minutes [ 0 ]
            Tobias Metzke-Bernstein made changes -
            Assignee Original: Tobias Metzke-Bernstein [ tobias.metzke ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Thorben Lindhauer made changes -
            Assignee New: Thorben Lindhauer [ thorben.lindhauer ]
            Resolution Original: Fixed [ 1 ]
            Status Original: Closed [ 6 ] New: Reopened [ 4 ]
            Thorben Lindhauer made changes -
            Fix Version/s New: 7.11.x [ 15373 ]

              Unassigned Unassigned
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: