-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RAC] [Observability] Enable the observability alerts, cases and ruleRegistry
feature flags by default
#105237
Comments
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
@cyrille-leclerc Can you help us understand what the criteria for moving out of experimental status should be? |
I'm also curious if we have settled on whether this will now be a BETA feature or just go right to GA from Experimental. |
related APM documentation changes: #100039 |
ruleRegistry
feature flags by default
@cyrille-leclerc Do we need any changes to the "experimental" callout when we change the feature flags to be enabled by default? |
@vinaychandrasekhar @hbharding what do you think about this? Do we keep the experimental banner as it is today? |
@cyrille-leclerc @weltenwort Yes I would like to review and suggest a couple of changes. Will discuss with @hbharding and will circle back here. Thanks |
📝 Summary
Currently the observability alerts and cases pages are hidden by default. Similarly, the alert index templates and indices are not created or updated and no alert documents are written on alert execution. The feature flags that control this should default to being enabled if we want this to be available to all users.
✔️ Acceptance criteria
xpack.ruleRegistry.write
is set totrue
by default.true
by default or removed.The text was updated successfully, but these errors were encountered: