Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[SLO] No data is considered good for time slices #181577

Closed
simianhacker opened this issue Apr 24, 2024 · 1 comment · Fixed by #181888
Closed

[SLO] No data is considered good for time slices #181577

simianhacker opened this issue Apr 24, 2024 · 1 comment · Fixed by #181888
Assignees
@kdelemme
Labels
Feature:SLO Team:obs-ux-management Observability Management User Experience Team

Comments

@simianhacker
Copy link
Member

Currently we calculate the a time slice SLI as goodSlices / totalSlicesRecorded, this means if you only have sporadic data for 7 days for a 30 day rolling window, the total slices is based on the 7 days and not the total "potential" slices which would be 43,200. We should calculate the time slices SLI using maxSlices - (totalRecorded - goodSlices) / maxSlices
@simianhacker simianhacker added Feature:SLO Team:obs-ux-management Observability Management User Experience Team labels Apr 24, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

@kdelemme kdelemme self-assigned this Apr 25, 2024
@kdelemme kdelemme mentioned this issue Apr 26, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kdelemme kdelemme

Labels
Feature:SLO Team:obs-ux-management Observability Management User Experience Team
Projects
None yet
Milestone
No milestone
3 participants
@simianhacker @kdelemme @elasticmachine