jaegertracing/jaeger

Enhance Kafka exporter to respect max message size

Open

#6,439 创建于 2024年12月29日

在 GitHub 查看
 (10 评论) (0 反应) (0 负责人)Go (18,974 star) (2,326 fork)batch import
enhancementgood first issuehelp wantedstorage/kafka

描述

This is a copy of the upstream issue https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/36982 that we encountered, creating a ticket here to track and for better discoverability.

Problem is described here: https://github.com/jaegertracing/jaeger/pull/6437#issuecomment-2564811186

贡献者指南

技术栈
gokafka
领域
backenddataobservability
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
GoKafkaOpenTelemetry exporter
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Review the upstream issue (https://github.com/open telemetry/opentelemetry collector contrib/issues/36982) and the linked PR (https://github.com/jaegertracing/jaeger/pull/6437) for context. The problem involves handling max message size in the Kafka exporter, possibly by splitting messages or respecting configuration. Focus on the exporter code in the Jaeger repository, likely in the `exporter/kafka` directory. Examine comments from maintainers for guidance on desired approach.