-
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] Create maintenance window #170422
Labels
Comments
kdelemme
added
epic
Team: Actionable Observability - DEPRECATED
For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge"
Feature:SLO
labels
Nov 2, 2023
paulb-elastic
removed
the
Team: Actionable Observability - DEPRECATED
For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge"
label
Nov 22, 2023
Pinging @elastic/obs-knowledge-team (Team:obs-knowledge) |
miltonhultgren
added
Team:obs-ux-management
Observability Management User Experience Team
and removed
Team:obs-knowledge
Observability Experience Knowledge team
labels
Dec 12, 2023
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
@grabowskit can you weigh in on whether this seems like a feature customers are asking for? I'm putting it in our backlog for now. |
Closing this as maintenance window can be implemented using a custom ingest pipeline since 8.16: #193628 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
🌵 Summary
Discussion: https://elastic.slack.com/archives/C044PV8EJ4X/p1698932725575739
We should (maybe?) handle maintenance window. From a product standpoint, how would it look like? And from an engineering standpoint, how would we implement that since our infra relies a lot on transforms?
Maybe some enrich policy could be used to add arbitrary metadata to the SLI rollup, which would be excluded from the summary process and other calculations like burn rate.
The text was updated successfully, but these errors were encountered: