[tracking] Jaeger v2 based on OpenTelemetry collector #4843
Description
Proposal: https://docs.google.com/document/d/1s4_6VgAS7qAVp6iEm5KYvpiGw3h2Ja5T5HpKo29iv00/view
This replaces the previous attempt: #3500.
Work tracked in the project Jaeger V2
Roadmap
Proof of concept
- A single binary with memory storage and all-in-one functionality
- Validate that the current storage configuration works for primary / archive storage.
- Default configuration solution (do not require config file for all-in-one)
- Demonstrate Kafka exporter / receiver (ideally from OTEL), compatible with existing Jaeger Kafka writer
- Define v2 storage API that operates on OTLP batches, see if internal & remote APIs can be identical
- Benchmarks [Jaeger v2] Run benchmarks #4869
Feature parity
- Extend configuration of
jaeger_storage_exporterto support all existing backends -- project in Jaeger's LFX Mentorship - 2024 Term 01, March - May #5084 - Metrics & Traces -- project in Jaeger's LFX Mentorship - 2024 Term 01, March - May #5084
- What to do with admin port / services -- [jaeger-v2] Document changes to admin port / services documentation#750
- Adaptive sampling processor -- project in Jaeger's LFX Mentorship - 2024 Term 01, March - May #5084
Prepare for Beta
- Add to integration tests
- Add to release pipeline
- Documentation
Prepare for GA
- Helm chart [Feature]: Support Jaeger-v2 Helm Chart helm-charts#534
- Operator [Feature]: Support Jaeger-v2 Operator jaeger-operator#2411
- Clarify https://github.com/jaegertracing/jaeger#version-compatibility-guarantees
Enhancements
- SPM built-in
- Integrate with OTEL collector builder
ocb - Print active configuration (unresolved: Print OTEL configuration #5223), Auto Generation of Component Configuration from metadata.yaml open-telemetry/opentelemetry-collector-contrib#27003
Metadata
Metadata
Assignees
Labels
Type
Projects
Status