Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3195 Sequential Camunda activity event log for Event Based Processes
  3. OPT-3280

Consolidate EventCount/Trace and Engine Import Architecture

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.0.0-alpha2, 3.0.0
    • None
    • backend
    • None

      Context:
      To not further deviate further from the existing import architecture consisting of scheduler, indexHandler, importservice and job in the domain of event based processes and thus making it harder to maintain similar behavior we have to consolidate both.

      AT:

      • the existing `EventStateProcessingService` is splitup into it's equivalent import components, including a dedicated scheduler
        • the overall architecture of the engine import is reused as apart from no engine being present the data flow and involved components are the same
        • abstract core components of the import shouldn't depend on the engineContext
      • package structure is cleaned up, `engine.importing` should be merged into `importing`

      Out of Scope:

      • major changes to the architecture should be avoided

        This is the controller panel for Smart Panels app

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

                Created:
                Updated:
                Resolved: