perfsonar / perfsonar/microdep
Adopt RFC 9544's Precision Availability Metrics
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 2
- Avg merge
- 3h 58m
- Merged PRs (30d)
- 42
Description
Consider applying terminology from RFC 9544 on Precision Availability Metrics for Microdep analytics. Parameters set "under the hood" of the current system should be made more visible (and potentially more configurable) and formally specified in line with Service Level Objectives. Results could be presented applying Violated Interval (VI), Severely Violated Interval (SVI), and Violation-Free Interval (VFI) terms.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading RFC 9544 and inspecting the current Microdep analytics implementation to identify parameters currently set under the hood. Define how SLO terminology and configuration should be specified, then determine how results should present VI, SVI, and VFI. Done means the terminology, parameter visibility, and intended configurability are clearly implemented and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- analytics, observability, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100