livepeer / livepeer/go-livepeer
add a few simple prometheus metrics
Open
Nobody has claimed this yet.
area: metrics
good first issue
help wanted
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
Please let me know if any of these already exist or if there are better ways to handle some of these situations.
livepeer_broadcaster_count—1if running with-broadcaster,0otherwiselivepeer_orchestrator_count—1if running with-orchestrator,0otherwiselivepeer_transcoder_count—1if running with-transcoder,0otherwise
These will let us sum the currently running counts of Bs, Os, and Ts without resorting to building the numbers from the local Kubernetes environment.
livepeer_gpu_count— If running as a-transcoderwith GPUs, how many GPUs are we running with?livepeer_gpu_nvidia_count— How many-nvidiaGPUs are we using?livepeer_gpu_vaapi_count— How many VAAPI GPUs are we using?
Contributor guide
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 checking the existing Prometheus metrics and the handling of the -broadcaster, -orchestrator, -transcoder, -nvidia, and VAAPI options. Compare the intended counts with monitoring/config-generator/src/generate.js around line 393. Done means the six requested metrics are exposed with correct values for each supported runtime configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100