-
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
[SLO] Add documentation for SLO functionality #147749
Comments
Pinging @elastic/actionable-observability (Team: Actionable Observability) |
We had a meeting with @mdbirnstiehl and @CoenWarmer yesterday, since we are not going in 8.7, the documentation team will start working on the documentation after they are done with the 8.7 released features. |
@mdbirnstiehl @ollyhowell I just wanted to let you know the SLO feature is going to be released as beta in 8.8. Let me know if you need any help regarding the documentation. |
@mdbirnstiehl @ollyhowell Can I help with this? |
Hi @kdelemme, we've been wrapping up work on things for the 8.7 release, so we haven't started work on the SLO documentation yet. This will be one of my priorities for 8.8. We are trying a new sprint schedule in Obs Docs where we work on non-release related work for the first 3 weeks after a release. Following that, we will work on release-related, which is where this will fall. You can maybe get a better overview of it from this view of my issues.. But I'm sure I'll need your help at that point and will reach out. Let me know if that makes sense or you have any questions. |
@mdbirnstiehl What's the status on this? |
Spoke with @mdbirnstiehl over Slack. The URL for docs will be: https://www.elastic.co/guide/en/observability/current/slo.html. |
📝 Summary
Part of #143216
If a user has no SLOs configured yet, the user will see a welcome message when visiting the SLO page.
The current designs contains links to a documentation page for SLOs:
The Elastic website should have documentation pages for use of the SLO functionality.
✅ Acceptance criteria
The text was updated successfully, but these errors were encountered: