-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Comments
We should also be able to specify the format of the spans, to allow us to accept Zipkin spans. |
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? |
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. |
I added a couple more tasks |
Hello, so what's the status of this? |
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. |
The last missing part is documentation. Which is tracked separately #1030 |
I know this issue was closed. |
In the current setup, |
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
The text was updated successfully, but these errors were encountered: