jaegertracing/jaeger

Enhance Kafka exporter to respect max message size

Open

#6439 opened on Dec 29, 2024

View on GitHub
 (10 comments) (0 reactions) (0 assignees)Go (18,974 stars) (2,326 forks)batch import
enhancementgood first issuehelp wantedstorage/kafka

Description

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

Contributor guide

Tech stack
gokafka
Domain
backenddataobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
GoKafkaOpenTelemetry exporter
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
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.