-
Notifications
You must be signed in to change notification settings - Fork 166
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
[DOCS] Observability Alerting - Enhancements to O11y Alerting doc #4609
Comments
Regarding deprecation, we do still identify Uptime as deprecated, as it will be removed at some point in the future (albeit not in v 9.0.0) |
I've updated the suggestions above |
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
cc @dedemorton Should we move this ticket to https://github.com/elastic/observability-docs repo? |
@maryam-saeidi Yes. I'll move it. |
That was intentional based on the conversation happening in the initial PR. If it's too confusing, we can remove content related to the SLI/SLO and just mention it instead. My question (#4345):
The answer I got from @shahzad31 (#4345 (comment)):
|
List all available alerts with the "real" name in the Kibana
On the documentation page Create and Manage Rules under Observability, I would recommend to use the real names and categorization we have in the UI.
From:
To:
Or create sections, one for each app.
Remove or rework the Uptime deprecation message(REMOVED)
Guidance on migrating from Uptime to Synthetics
In this section, I think we're mixing up SLI/SLO with Alerting. I do not know how we can make this visible. Maybe we should add a warning migration banner in all the Uptime sections to hint to the fact one is invited to move to Synthetics.
Prerequisites for APM - Anomaly rule
The
APM - Anomaly rule
requires Machine Learning. ML features require Platinum license.Suggest the data being queried on each alert type
It would be handy to have an hint to which data stream / data view / index pattern each kind of rule uses.
E.g. for APM, one might think the user is allowed to use all the data from the
traces-apm*
data streams, while it's not true.This might be covered in a separate issue and provide in-product hints about each alert.
FYI @paulb-elastic, @jasonrhodes
Not urgent, but it would be nice to address this in the future.
The text was updated successfully, but these errors were encountered: