[Synthetics] Remove auto-creation of default monitor status and TLS alerts

[justinkambic]

Summary

Resolves #193610.

This PR overhauls the way that we check for rules to display in the UI. This is necessitated because we are no longer automatically generating rules, and the global rules we can use are of the same type as the customizable rules users can define.

UI changes

• We will display a callout to the user notifying them that there are no Monitor Status rules, if they have any monitor running with alerting enabled.
• We will display a callout to the user notifying them that there are no TLS rules, if they have HTTP monitors defined (with alerting enabled) but no TLS alerts running.
• We will display a callout to the user if there's no default connector defined.

This is very similar to what we already do, but the method of querying the data has changed, and it's stored in the application state now.

Backend changes

Users can still create the default alerts, and thus the API for this is still present, but it's not called by default anymore. If the user navigates to Synthetics and starts creating monitors, they'll eventually be prompted by the callouts above. We do plan to follow this up with a better UI experience, which we have designs for, but I will create that as an enhancement ticket linked to this one that we can prioritize later. These changes are largely in line with what the current experience is, so this is not regressive.

We have also removed defaultStatusRuleEnabled and defaultTLSRuleEnabled from the settings saved object definition, per the requirements in the linked ticket.

Checklist co-opted from the linked issue

• The default monitor status and tls rules should no longer be created when the user visits the Synthetics app
• In the Settings view, the toggles to enable and disable the rule should be removed
• References to the status/tls rule enabled settings (defaultStatusRuleEnabled and defaultTlsRuleEnabled) within the Synthetics saved object should be removed from the code base, particularly from the default_alert_service.ts file.
• Default rules, both TLS and Monitor Status, should be able to be enabled/disabled and deleted from the Rule management page
• If a Synthetics monitor status rule is not present, either the default or a custom rule, a callout should be displayed on the Synthetics overview page with a call to action button to create either the default alert or a custom alert.
• If the default TLS rule is not present, the callout should also include a call to action to create a TLS rule

Code is WIP.

[elasticmachine]

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[dominiqueclarke]

I think I would only display this if there is a DEFAULT rule present. The default connectors are irrelevant if there isn't any default rules. For example, if the user is only using custom rules, configuring default connectors is irrelevant.

In my opinion, this button should navigate to the observability rules management page

[dominiqueclarke]

When I click on "create custom rule" and it's created, the callout remains until I refresh the page.

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: b9632f5

Failed CI Steps

• Quick Checks

History

• 💔 Build #254606 failed 2773205
• 💔 Build #252768 failed 4dec151
• 💔 Build #252094 failed dbc28e4
• 💔 Build #252085 failed 230e5ec
• 💔 Build #252073 failed 7c3ba2f

cc @justinkambic