Requirement - what kind of business use case are you trying to solve?
Kafka supports a lot of parameters and Jaeger provide the user only a handful (Brokers, topic, group-id).
Problem - what in Jaeger blocks you from solving the requirement?
Jaeger should be able support a parameter for API version.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Add them in the configuration of the ingester and collector.
Other relevant parameters:
- Producer.RequiredAcks
- Producer.CompressionLevel
- Consumer.Fetch.Default
Any open questions to address
What other parameters should be supported by jaeger?
(I'll will try to tackle this issue when I'll have time but help or feedback on parameters to add would be very nice)
Requirement - what kind of business use case are you trying to solve?
Kafka supports a lot of parameters and Jaeger provide the user only a handful (Brokers, topic, group-id).
Problem - what in Jaeger blocks you from solving the requirement?
Jaeger should be able support a parameter for API version.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Add them in the configuration of the ingester and collector.
Other relevant parameters:
Any open questions to address
What other parameters should be supported by jaeger?
(I'll will try to tackle this issue when I'll have time but help or feedback on parameters to add would be very nice)