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

Robust incremental import of Workflow Data

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • L3 - Default
    • 1.0.0, 1.0.0-alpha2
    • None
    • None
    • None

    Description

      AT

      • given
        • As a user I can configure the REST endpoint of a Camunda Engine
      • Once
        • Optimize is started
      • then
        • it starts indexing
        • Indexing fault tolerant
        • Indexing is incremental

      Things to check

      • are updates happening on Historical activity table records?
      • is it possible to perform sorted query?
      • do we need extra hashing on entities in engine?
      • is it possible to request only the data since last indexing from the engine?
      • should partial imports be allowed for statistics, i.e. heatmap, etc.?
      • how to handle load balancing on engine resources, make sure we don't block network\io\cpu with our import requests?
        • do we run against clustered engines?
      • how to handle performance\load balancing on ES nodes\cluster?
        • do we test against multiple nodes of ES?
      • what are common pitfalls that other people face?
      • how do we handle FK's\joins?
        • do we denormalize data?
        • do we import only tables which are used in Optimize right now?
      • should it be possible to configure periodical indexing?

      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. OPT-131 The import of workflow data is triggered automatically

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

            Task - A task that needs to be done. OPT-132 The import of workflow data is retriggered in periods

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

            Task - A task that needs to be done. OPT-136 During the import of the workflow data only missing data is imported to elasticsearch

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

            Task - A task that needs to be done. OPT-137 The import of engine data is done in pages

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

            Task - A task that needs to be done. OPT-139 The import of data is done in jobs

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

            Task - A task that needs to be done. OPT-176 I can see documentation about how the import is done in optimize

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

            Activity

              People

                Unassigned Unassigned
                meyer Daniel Meyer
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce