Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Propose Jaeger project for LFX Mentorship '23 Term 02 June - August #947

Merged
merged 1 commit into from
May 1, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions programs/lfx-mentorship/2023/02-Jun-Aug/project_ideas.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,4 +17,20 @@

## Proposed Project ideas

### Jaeger

#### Upgrade Jaeger's internal telemtery to OpenTelemetry

- Description: historically, the Jaeger backend used the OpenTracing API, with Jaeger's own Go SDK `jaeger-client-go`, for instrumenting its own internals for distributed tracing. Since Jaeger's SDKs have been deprecated, we want to upgrade the Jaeger backend to use the OpenTelemetry tracing API and SDK directly.
- Expected Outcome:
- Replace the use of OpenTracing API with OpenTelemetry
- Remove `jaeger-client-go` and `jaeger-lib` as dependencies
- Remove `opentracing-go` and `opentracing-contrib/*` as dependencies
- Switch to standard instrumentation libraries where available (e.g. for HTTP, gRPC)
- Rethink/rework `crossdock` integration tests to test end-to-end flow with OpenTelemetry data
- Publish a blog post on medium.com/jaegertracing documenting the experience
- Recommended Skills: Go
- Mentor(s): Yuri Shkuro (@yurishkuro, [email protected])
- Upstream Issue: https://github.com/jaegertracing/jaeger/issues/3381

---