P K Navin Shrinivas

Hey @yaleman why is this tagged blocked? Also, the merged PR seems to solve almost everything...does this still require some cleanup? As for forwarded IPs, does Axum get details about...

Hey, I'd like to work on this!

Hey, I'd like to try this Just to warrant my understanding : - First include `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) -...

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] )...

Hey, are you waiting for commits to meet the test requirement? I'd like to more this pr forward with necessary changes

> thanks! It was fun working on this issues. Learnt a lot :) , any other issue that i can work on that are beginner friendly?

From what I can understand this task is majorly in the frontend, is there an issue this links to the Jaeger-ui repo?

also, @charconstpointer Do you by any chance have the otel collector exported file with you? Will help me replicate and implement this feature.

> 1. I disagree about the "majority", I think defining a conversion service is more work. There already exists endpoints such as '4317' in Jager Backend that can accept OTLP...

Ah! That makes sense, I think I have a grip on the issue now and I went through the code a fair bit and found `otlp2jaeger` package that I think...