Add gRPC RED metrics and tracing to the Stargate Kubernetes router
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Why
The Stargate Kubernetes router proxies worker registration and Stargate watch streams across a network boundary. Its reverse-tunnel counters are now available at startup, but the gRPC proxy path does not expose RED metrics or OpenTelemetry spans. Operators need bounded request, error, and duration signals plus propagated trace context before enabling this path in production.
What
- Add pre-initialized request and error counters for
WatchStargatesandRegisterInferenceServer. - Add request-duration histograms with bounded method and status labels.
- Create inbound and outbound OpenTelemetry spans using stable
service.operationnames. - Extract and propagate W3C Trace Context on forwarded gRPC calls.
- Add tests for startup-visible metrics, success/error observations, and trace propagation.
Related
Relates to #502.
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 locating the Stargate Kubernetes router's gRPC proxy path for WatchStargates and RegisterInferenceServer, then inspect how startup metrics and reverse-tunnel counters are initialized. Add the requested RED metrics, OpenTelemetry spans, and W3C Trace Context handling, with tests covering startup visibility, success/error observations, and propagation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc, kubernetes
- Domain
- cloud, networking, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100