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? Please describe.
Hi guys, I have the following problem: I was testing the Alerting plugin and as stated in the documentation, basically every monitor and destination that is created is visible to every user, except if the following setting is applied:
PUT _cluster/settings
{
"transient": {
"plugins.alerting.filter_by_backend_roles": "true"
}
}
With this option it is possible depending on the backend role to restrict the display of monitors and destinations.
My OpenSearch is connected to a LDAP-Server and in my company there are hundreds of AD-Groups which my OpenSearch resolves all as backend roles. All of us in the company share several AD-Groups and as specified in the documentation the separation of monitors and destinations only works if no backend role is shared.
Setting the resolve_nested_roles option to false excludes all roles that are nested but still leaves several that are not.
Even if I use the nested_role_filter parameter this only applies to nested roles and leaves out all those that are not.
Describe the solution you'd like
It would be a great improvement to have the possibility to separate the Monitoring and Destinations according to Tenant or to really be able to filter out all unnecessary roles.
Thanks in advance to anyone wo will take a look into it.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Hi guys, I have the following problem: I was testing the Alerting plugin and as stated in the documentation, basically every monitor and destination that is created is visible to every user, except if the following setting is applied:
With this option it is possible depending on the backend role to restrict the display of monitors and destinations.
My OpenSearch is connected to a LDAP-Server and in my company there are hundreds of AD-Groups which my OpenSearch resolves all as backend roles. All of us in the company share several AD-Groups and as specified in the documentation the separation of monitors and destinations only works if no backend role is shared.
Setting the resolve_nested_roles option to false excludes all roles that are nested but still leaves several that are not.
Even if I use the nested_role_filter parameter this only applies to nested roles and leaves out all those that are not.
Describe the solution you'd like
It would be a great improvement to have the possibility to separate the Monitoring and Destinations according to Tenant or to really be able to filter out all unnecessary roles.
Thanks in advance to anyone wo will take a look into it.
The text was updated successfully, but these errors were encountered: