-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
2
-
Not defined
-
3 - Expected
What is the desired functionality that you are missing?
Currently, the Camunda BPM engines from which Optimize imports data, have to be configured in a configuration file. To change the configuration, e.g. to add a new engine, the file has to be changed manually and Optimize has to be restarted. In more decentralized scenario with several stand-alone engines, this approach potentially leads to issues.
Potential solution: A functionality to configure the target optimize instance in the camunda engine. The engine registers itself with Optimize on startup via API-calls and without manual actions.
Which problem are you going to solve with this functionality?
This would allow it to transfer the responsibility for the engine configuration to decentralized teams running these engines, while also keeping one central Optimize instance. There would be no manual effort to configure engines in Optimize for the team taking care of Optimize.
This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10885. Please use this link for any future references and continue any discussion there.