Elastic Cloud - Changing slack connector in one monitoring setup impacts the other one

[bharvidixit]

Kibana version:
7.10.1

Elasticsearch version:
7.10.1

Server OS version:

Browser version:
Google Chrome Version 77.0.3865.120

Browser OS version:
Linux Ubuntu 20

Original install method (e.g. download page, yum, from source, etc.):
Elastic Cloud Enterprise Edition

Describe the bug:
I have two separate deployments (One for production and one for staging) on my Elastic cloud account and I am sending logs and metrics from both of these deployments to a common deployment (Elastic observability).
Now on my Elastic observability kibana, i have configured two slack separate slack connectors. One for staging and another for production.

I want to send all my production alerts to production slack connector and staging alerts to staging connector. But when i am making changes for slack connector on any of the alert the same slack connector setting get's applied on the other one as automatically.

Steps to reproduce:

1. Go toStack Monitoring on Kibana
2. If you have multiple clusters listed, configure alerts for cluster overview health alert for each cluster.
3. Try making changes in one of the cluster overview health alert and check if same gets applied on another (slack connector will automatically gets changed)

Expected behavior:

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

[elasticmachine]

Pinging @elastic/stack-monitoring (Team:Monitoring)

[ravikesarwani]

7.10 does not support multiple rules/alerts for the same rule/alert type and so in 7.10 you cannot set different slack connector for each cluster (you are monitoring) if you are consolidating monitoring data from different clusters into the same monitoring cluster.

In 7.10 the way to do that would be to setup separate monitoring cluster if you want to manage different configurations for different clusters being monitored (including thresholds, connectors etc.).

I want to add that we are working to get that addressed. In 7.15 we added the capability for the users to create multiple rules of the same rule type (#106457). We are also working to add filtering capability (#96800) so that users can create different rules and target different thresholds, connectors for different clusters.