livepeer / livepeer/stream-tester
Make stream-tester alerting actionable
Open
- Dominant language
- Go
- Stars
- 24
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Should go through Grafana like everything else and ideally not alert/page unless there's a genuine problem (probably multiple failed runs in succession)
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating the stream-tester alerting path and how it connects to Grafana, then review existing alert behavior and failure reporting. Done means alerts are routed through Grafana and avoid paging for isolated failures, while surfacing a genuine problem such as repeated failed runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grafana
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100