Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE]Support separation of alerts/monitors/destinations based on tenants/workspaces #708

Open
smuthukaruppannp opened this issue Sep 7, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@smuthukaruppannp
Copy link

Is your feature request related to a problem?
A large organization is most likely to have multiple administrators for managing cluster resources. For example, admin_a and admin_b could be responsible for managing indices index_x, index_y and associated resources such as alerts and monitors. Similarly admin_a, admin_c could be responsible for index_z.

Alerting does not have a concept of ownership, any user with the right permissions can read/delete alerting resources. #138 provided some segmentation based on backend roles.

To ease the administrative process, Dashboard tenancy provides a way to group related objects together although such support is only available for Dashboard objects such as visualizations, index patterns. For cluster owned items such as alerting, tenancy separation is not available. For example, in the above scenario, admin_a would like to group index_x and index_y related Information in one tenant and index_z in another tenant. Such tenant separation is currently available for items such as index patterns but for plugin objects like monitors.

What solution would you like?
Would like the ability to group not only Dashboard objects but Cluster/Plugin/Extension objects (specifically alerting) with tenants/workspaces

Possible approaches could be to store references to the alerting objects as part of Dashboard tenants or store tenant information as metadata in the alerting object which can then be used later as filter during display.x

What alternatives have you considered?
Considered #138 but is has few drawbacks. It does not address scenarios such as the one mentioned, requires additional backend roles to be created in some instances and end users need to be aware of backend roles that need to be mapped.

Do you have any additional context?
Add any other context or screenshots about the feature request here.

@smuthukaruppannp smuthukaruppannp added enhancement New feature or request untriaged labels Sep 7, 2023
@dblock dblock removed the untriaged label Jun 6, 2024
@dblock
Copy link
Member

dblock commented Jun 6, 2024

[Triage -- attendees 1, 2, 3, 4, 5, 6, 7]

Looks like a good feature request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants