[Alerting] Include stack monitoring rules in import/export

[ymao1]

We have enabled import/export of rules through the SO management UI via this PR but are currently excluding stack monitoring rules from being exported via this UI.

There are multiple issues open that need to be addressed before stack monitoring rules can be exportable via the framework export, so once those issues are resolved, we should make sure that stack monitoring rule export is enabled.

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[mikecote]

Blocked until the following issues are resolved: https://github.com/elastic/kibana/issues?q=is%3Aopen+is%3Aissue+label%3A%22Epic%3A+Stack+Monitoring+Alerting+Alignment%22

[ymao1]

#106457 has been merged, which should unblock this issue. Should verify that with those changes, if stack monitoring rules are enabled for export, duplicate stack monitoring rules will not be created.

[ymao1]

@jasonrhodes With #106457, this is the potential behavior if stack monitoring rules are enabled for export via Saved Objects Management:

Scenario 1:
Kibana A -> has 8 OOTB stack monitoring rules created and other rules. No changes made to OOTB rules
Kibana B - > has 8 OOTB stack monitoring rules created

User exports all rules from Kibana A and imports them into Kibana B, default space

User sees 16 stack monitoring rules, with duplicate Rule names:

Scenario 2:
Kibana A -> has 8 OOTB stack monitoring rules created in Default space

User goes to Different Space and tries to Create default rules. Nothing is created.
User exports all rules from Kibana A Default space and imports them into Kibana A Different Space.
User sees 8 stack monitoring rules in Different Space

Are these scenarios acceptable?

[bduong97]

Hi all, will this feature be revisited? We'd like to include all rule types in a saved object export if possible.