Document Kafka storage usage

[jpkrohling]

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

Use the new Kafka storage.

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

Lack of documentation about it.

Proposal - what do you suggest to solve the problem or improve the existing situation?

Document it:

• How to start the components (standalone/query/collector) with the new storage
• What configuration options there are
• Gotchas (write-only!)
• Bonus points: how to start Kafka for development purposes (Docker?)
• Missing bits (the component that ingests data and writes to Cassandra/Elasticsearch)

[PikBot]

Are there some resources available as a starting point? I don't have much knowledge myself about Kafka storage but I would like to help out with this issue.

[yurishkuro]

cc @vprithvi

[vprithvi]

@PikBot There aren't any resources apart from the code at this juncture. I'm familiar with Kafka and can write a skeleton doc that we can iterate on.

[PikBot]

@vprithvi that would be helpful.

Also can you share the link to the code? I can go through it and try to understand it from a technical point of view.

[vprithvi]

@PikBot The code for emitting to Kafka is at https://github.com/jaegertracing/jaeger/tree/master/plugin/storage/kafka

We are working on releasing the code for consuming from Kafka and writing to Cassandra, it's being tracked as part of jaegertracing/jaeger#929

I didn't mention this earlier, but thanks for your offer to help!!!

[PikBot]

@vprithvi thanks! I'll try my best to get it documented. An initial skeleton doc from your side would be nice!