Alerts and Rules Views to GA

[emma-raffenne]

Remove Technical Preview flag and disclaimer for Observability Alerts and Rules views, remove experimental feature flags from source code and update documentation accordingly.

Should include:

• Rule details page - Phase 1 #129777
• [Actionable Observability] Alerts as Data experimental fields #133584

Implementation

• [Actionable Observability] Remove rules feature flag #132598
• [Actionable Observability] Remove alerting experimental feature flags #133583
• [Actionable Observability] Remove technical preview component and disclaimer from Observability views #134161

[emma-raffenne]

GA for 8.3 will depend on decision regarding custom fields in alert-as-data.

[mgiota]

As part of this ticket do we also want to remove all experimental flags from our source code? Here are the flags we currently use:

• xpack.observability.unsafe.cases.enabled
• xpack.observability.unsafe.alertingExperience.enabled
• xpack.ruleRegistry.enabled
• xpack.observability.unsafe.rules.enabled
• xpack.ruleRegistry.write.disabledRegistrationContexts

Let's discuss during our Weekly Meeting and we can create a new sub ticket accordingly.

cc @emma-raffenne @simianhacker

[mgiota]

GA for 8.3 will depend on decision regarding custom fields in alert-as-data.

@emma-raffenne Let's clarify during our Weekly meeting what do you mean by custom fields. In alerts-as-data terms we currently have technical fields and experimental fields. Do you refer to experimental fields or is custom fields something else?

[emma-raffenne]

@mgiota It refers to fields in alerts-as-data indices that refer to specific rule types and are not generic to all type of alerts.

[mgiota]

@emma-raffenne I see! Custom fields in this case is what I called experimental fields, so we are on the same page regarding this. Let me know how I can help there, since I have quite a bit of background there. I was working on these experimental fields and on an RFC document together with security team.