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

Kafka Ingester #929

Closed
8 of 9 tasks
davit-y opened this issue Jul 11, 2018 · 10 comments
Closed
8 of 9 tasks

Kafka Ingester #929

davit-y opened this issue Jul 11, 2018 · 10 comments

Comments

@davit-y
Copy link
Contributor

davit-y commented Jul 11, 2018

Requirement - what kind of business use case are you trying to solve?

An Ingester allows users to queue spans in Kafka instead of writing directly to storage in Collector. The Ingester consumes spans from a configurable Kafka topic and writes to any number of desired storage types.

Problem - what in Jaeger blocks you from solving the requirement?

This kind of queueing functionality will be new to Jaeger.

Checklist

@yurishkuro
Copy link
Member

We should also be able to specify the format of the spans, to allow us to accept Zipkin spans.

@yurishkuro
Copy link
Member

Are we planning to support multiple writers in the ingester? If so, you may need to address separate Kafka reader/writer configurability. Is there a plan how it will be done?

@davit-y
Copy link
Contributor Author

davit-y commented Jul 12, 2018

Yes, we will support multiple writers. The configuration for the writers will use the current storage factory configuration flags. For the consumer we will have separate Kafka/consumer options (Brokers,Topic,GroupID,Parallelism) similar to the CollectorOptions.

@yurishkuro
Copy link
Member

I added a couple more tasks

@yurishkuro
Copy link
Member

@Dieterbe
Copy link
Contributor

Dieterbe commented Aug 9, 2018

Hello,
this sounds interesting to me. Since we are looking to process spans with some custom logic and analyze traces to generate reports.
I know we could probably already do something like this using flink, but we're new to that, whereas we're quite familiar with kafka.

so what's the status of this?

@black-adder
Copy link
Contributor

If all you care about is reading spans from kafka directly, you can configure the collector to dual write to cassandra and kafka. We need to cut a new release to enable that feature but it should already be available in master.

@pavolloffay
Copy link
Member

The last missing part is documentation. Which is tracked separately #1030

@bohea
Copy link

bohea commented Oct 25, 2018

I know this issue was closed.
but if jaeger-ingester consuming spans from kafka
who is playing role of producer sending spans to kafka, is jaeger-agent or jaeger-client?

@vprithvi
Copy link
Contributor

In the current setup, jaeger-collector sends spans to Kafka

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants