-
Notifications
You must be signed in to change notification settings - Fork 621
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add Jaeger projects for 2024 Term-1 (#1108)
* Add Jaeger projects for 2024 Term-1 Signed-off-by: Yuri Shkuro <[email protected]> * Add 2nd mentor Signed-off-by: Yuri Shkuro <[email protected]> --------- Signed-off-by: Yuri Shkuro <[email protected]>
- Loading branch information
1 parent
48fb6ef
commit 0c4a2f5
Showing
1 changed file
with
32 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -18,4 +18,36 @@ | |
|
||
## Proposed Project ideas | ||
|
||
### Jaeger | ||
|
||
#### Jaeger-V2 Storage Backends | ||
|
||
- Description: Jaeger is a distributed tracing platform. Jaeger V2 is a major new version where we rebase all Jaeger backend components (agent, collector, ingester, and query) on top of the OpenTelemetry Collector. Currently only memory storage is wired in v2, we need to add Elasticsearch, Opensearch, Cassandra, Badger. | ||
- Expected Outcome: Build out full support in jaeger-v2 for all storage backends supported by jaeger-v1 | ||
- Recommended Skills: Go, scripting, CI/CD | ||
- Mentor(s): | ||
- Yuri Shkuro (@yurishkuro, [email protected]) | ||
- Jonah Kowall (@jkowall, [email protected]) | ||
- Upstream Issue: https://github.com/jaegertracing/jaeger/issues/5084 | ||
|
||
#### Jaeger-V2 Observability | ||
|
||
- Description: Jaeger is a distributed tracing platform. Jaeger V2 is a major new version where we rebase all Jaeger backend components (agent, collector, ingester, and query) on top of the OpenTelemetry Collector. Currently jaeger-v2 components are initialized without observability clients. We need to instantiate appropriate logging, tracing, and metrics clients and pass them to the components. The existing code uses internal metrics API, which needs to be bridged to OTEL metrics to minimize code changes. | ||
- Expected Outcome: Achieve parity in observability of jaeger-v2 compared to jaeger-v1 | ||
- Recommended Skills: Go, scripting, CI/CD | ||
- Mentor(s): | ||
- Yuri Shkuro (@yurishkuro, [email protected]) | ||
- Jonah Kowall (@jkowall, [email protected]) | ||
- Upstream Issue: https://github.com/jaegertracing/jaeger/issues/5084 | ||
|
||
#### Jaeger-V2 Adaptive Sampling | ||
|
||
- Description: Jaeger is a distributed tracing platform. Jaeger V2 is a major new version where we rebase all Jaeger backend components (agent, collector, ingester, and query) on top of the OpenTelemetry Collector. Jaeger-v1 collector can serve sampling configuration to SDKs, and allows either static configuration (with hot reload) or adaptive sampling that continuously re-calculates the desired sampling probabilities. We need to enable all these capabilities in jaeger-v2. | ||
- Expected Outcome: Support adaptive sampling in jaeger-v2 | ||
- Recommended Skills: Go, scripting, CI/CD | ||
- Mentor(s): | ||
- Yuri Shkuro (@yurishkuro, [email protected]) | ||
- Jonah Kowall (@jkowall, [email protected]) | ||
- Upstream Issue: https://github.com/jaegertracing/jaeger/issues/5084 | ||
|
||
--- |