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.