-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
-
2
-
M
-
2 - Flawed
What is the desired functionality that you are missing?
As an Optimize Admin in an engine multi-tenancy setup (a single Process Engine With multiple Tenant-Identifiers), I would like to be able to define which tenant-specific process data is actually being imported into an Optimize instance.
Which problem are you going to solve with this functionality?
Currently as an Optimize Admin I cannot configure which tenant-specific process data is being imported into Optimize. Per default all tenant data is being imported into Optimize. There are use-cases where an Optimize instance should only handle process data from specific tenants and not all. This leads to a lot of overhead during import and also storage in Elasticsearch.
Hint:
- This change requires work in the Optimize Rest API in the Camunda Engine
- We should avoid a FE solution where possible. One idea is to directly edit a config file
This is the controller panel for Smart Panels app
[OPT-5246] Exclude data import from specified tenants to improve resource efficiency
Link | New: This issue is depended on by SUPPORT-10606 [ SUPPORT-10606 ] |
Labels | New: potential_for_next_quarter |
Labels | Original: potential_for_next_quarter | New: potential_for_3.6 potential_for_next_quarter |
Status | Original: Open [ 1 ] | New: Scheduled [ 10912 ] |
Optimize PM Priority | New: Ranked higher |
Optimize PM Priority | New: Ranked higher |
Fix Version/s | New: 3.6.0 [ 16894 ] |
Description |
Original:
What is the desired functionality that you are missing?
Which problem are you going to solve with this functionality? Context: Given, When, Then Hint: |
New:
*What is the desired functionality that you are missing?*
As an Optimize Admin in an engine multi-tenancy setup, I would like to be able to define which tenant-specific process data is actually being imported into an Optimize instance. *Which problem are you going to solve with this functionality?* Currently as an Optimize Admin I cannot configure which tenant-specific process data is being imported into Optimize. Per default all tenant data is being imported into Optimize. There are use-cases where an Optimize instance should only handle process data from specific tenants and not all. This leads to a lot of overhead during import and also storage in Elasticsearch. Hint: * This change requires work in the Optimize Rest API in the Camunda Engine |
Mentioned Roles |
Mentioned Groups |