Closed yurishkuro closed 2 months ago
Hey, I'd like to try this
Just to warrant my understanding :
Kafka
configurations in the config files ( receiver : https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/kafkareceiver/README.md and exporter : https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/kafkaexporter/README.md)I'm assuming here that the single v2 binary is responsible for ingesting and querying this means
yes but it can be configured to run in different roles
Will export data to various stores(using kafka)? [Im Not sure about this point] OR are we testing if otel exporters can export jaeger traces to kafka?
the "collector" mode will be receiving spans over network, e.g. OTLP receiver, and using Kafka exporter to write them to Kafka. The "ingester" mode will be using Kafka receiver and then using Jaeger storage exporter to persist in a database.
We only seem to be providing one config.yaml (which I assume includes config for both collector and ingester, as mentioned in the doc [Option 2 (selected): shared runtime component] ) So the config will look something like this : On collector end :
extensions:
jaeger_storage:
kafka:
kafka_traces:
kafka_topic: traces
exporters:
jaeger_storage_exporter:
trace_storage: kafka_traces
I'm still not sure how the "ingester" (Which I think is the "jeager_storage" is able to reference another Jaeger storage (Kafka). Also, are these features even supported and implemented in the v2 binary (To read something like the above config file)?
@NavinShrinivas see examples I added to the issue description. There is no explicit interaction required between Kafka components and jaeger_storage
.
@yurishkuro Is this WIP or needed to work on for those not has any merged PRs:
@james-ryans has it
@james-ryans Any updates here?
@james-ryans Any updates here?
The PR addressing this issue is #4971 and is currently in progress but is blocked by an upstream issue at otelcol-contrib#30789. I haven't received enough context to assist in fixing the upstream issue, as we have prioritized adding full support for Jaeger-v2 storage backends. I'll return to this once our priorities have been addressed.
Part of #4843
Objective
jaeger-v2
as a replacement forjaeger-collector
/jaeger-ingester
Design
We want to rely on OTel's usual pipeline setup, which should allow us to use OTel's Kafka receiver and exporter without changes. For example, this is how it might look
Replacement for jaeger-collector
Replacement for jaeger-ingester
Steps
jaeger-ingester
supports today