Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-6076

Log full original elasticsearch exception in ElasticsearchStatusExceptionMapper

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.8.0
    • None
    • None
    • None
    • Not defined

      Context:
      Whenever an ElasticsearchStatusException occurs e.g. during report evaluation it's catched and mapped to an error response via `ElasticsearchStatusExceptionMapper`.
      The Optimize API error message contains the content of `message` from the original exception which is usually suffice for the Optimize API error response.

      However it would be helpful to still log the full original ElasticsearchStatusException in the Optimize log for easier debugging in such cases.

      AT:

      • when an ElasticsearchStatusException occurs the `ElasticsearchStatusExceptionMapper` should log the full original exception

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              sebastian.bathke Sebastian Bathke
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: