liquidmetal-dev / liquidmetal-dev/battery
Distributed tracing (OpenTelemetry) across poolmgrd/hostagent/flintlock calls
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 13m
- Merged PRs (30d)
- 33
Description
Add OpenTelemetry tracing spans across poolmgrd -> poolmgr-hostagent -> flintlock gRPC calls to make cross-service latency and failures easier to diagnose, complementing the existing Prometheus metrics (#13).
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 tracing the existing gRPC call paths from poolmgrd through poolmgr-hostagent to flintlock, and inspect the Prometheus metrics work in issue #13 for related instrumentation points. The work is done when cross-service latency and failures can be followed through OpenTelemetry spans across these calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- distributed-systems, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100