You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?
Currently, the Trace Analytics OpenSearch Dashboards plugin does not support the option for tenants to only have access to their own namespaced indices causing the plugin to fail.
What solution would you like?
At some point this commit was made to extend the indices pattern. However this pattern is too broad for individual tenants, causing the application to return a 403 based on security rules. We would like the pattern to include the name of the tenant so it's easier to limit access to particular index patterns. Therefore we came with the following solution:
What alternatives have you considered?
As far as we know there are no existing solutions for the problem.
Do you have any additional context?
We already started working on a feature proposal and made sure it was fully functional on our test environment. The next step would be to get it upstream. The feature can be enabled or disabled based on the following configuration option: opensearch_observability.multitenancy.enabled: true
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Currently, the Trace Analytics OpenSearch Dashboards plugin does not support the option for tenants to only have access to their own namespaced indices causing the plugin to fail.
What solution would you like?
At some point this commit was made to extend the indices pattern. However this pattern is too broad for individual tenants, causing the application to return a 403 based on security rules. We would like the pattern to include the name of the tenant so it's easier to limit access to particular index patterns. Therefore we came with the following solution:
otel-v1-apm-span-* => otel-v1-apm-span-*
otel-v1-apm-service-map* => otel-v1-apm-service-map-*
What alternatives have you considered?
As far as we know there are no existing solutions for the problem.
Do you have any additional context?
We already started working on a feature proposal and made sure it was fully functional on our test environment. The next step would be to get it upstream. The feature can be enabled or disabled based on the following configuration option:
opensearch_observability.multitenancy.enabled: true
The text was updated successfully, but these errors were encountered: