Actions
action #158556
closedopenQA Project (public) - coordination #127031: [saga][epic] openQA for SUSE customers
openQA Project (public) - coordination #152955: [epic] Metric-driven project management in SUSE QE Tools team
Single-value SLI of OSD HTTP response code successful vs. all size:S
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2024-04-07
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Motivation¶
See https://progress.opensuse.org/issues/158550
Acceptance criteria¶
- AC1: https://monitor.qa.suse.de/ shows single-value OSD response code based "availability" as percentage
- AC2: An according alert exists
Suggestions¶
- Understand which status-codes we care about
- Calculate a ratio between them, nr(!5xx)/nr(all)?
- Put a single value panel on monitor.qa.suse.de, similar to already existing availability
- Define a threshold to visualize based on current data, e.g. if we have 98% then mark everything below 95% as red
- Define an according alert, same or similar to visual threshold
- Out-of-scope: traffic between workers or OSD<->workers
Actions