Add an otelcol.exporter.kafka component

[ptodev]

PR Description

Adding a new otelcol.exporter.kafka component based on the OTel Collector's kafka exporter.

Which issue(s) this PR fixes

Fixes #290

PR Checklist

• CHANGELOG.md updated
• Documentation added
• Tests updated
• Config converters updated

[hainenber]

I wonder if we still need to implement an equivalent otelcol-to-Alloy converter, similar to these? 🤔

[mattiasnensen]

Something that is worth looking at is whether or not the fix exists in Grafana Alloy so sasl mechanism AWS_MSK_IAM actually works. Please look at this issue: open-telemetry/opentelemetry-collector-contrib#32500

[ptodev]

@hainenber True, I added the converters now :)

@mattiasnensen Unfortunately I think Alloy will only pick up the change once the upstream exporter has implemented it. If you need to reach out to the Otel maintainers you could open an issue in the Contrib repo or send a message on the CNCF slack. As a last resort you could also just open another PR which is inspired by the closed one that you are interested in. The Alloy team also contributes upstream, but in this case it doesn't seem to be a critical issue and more of a missing feature? In that case I honestly don't think we'd have bandwidth for it, since we're a bit preoccupied with more urgent work :/

[mattiasnensen]

@hainenber True, I added the converters now :)

@mattiasnensen Unfortunately I think Alloy will only pick up the change once the upstream exporter has implemented it. If you need to reach out to the Otel maintainers you could open an issue in the Contrib repo or send a message on the CNCF slack. As a last resort you could also just open another PR which is inspired by the closed one that you are interested in. The Alloy team also contributes upstream, but in this case it doesn't seem to be a critical issue and more of a missing feature? In that case I honestly don't think we'd have bandwidth for it, since we're a bit preoccupied with more urgent work :/

It was reported here but it was closed: open-telemetry/opentelemetry-collector-contrib#19747

Then this issue was created which allegedly fixed the issue, but the contribution wasn't accepted as the contributor didn't have a signed CLA: open-telemetry/opentelemetry-collector-contrib#32500

Best regards,

[wildum]

One additional comment: can you update the link to the otel component in your PR please? It points to the v0.96.0 version but the one implemented here is the v0.101.0

[wildum]

LGTM!

[clayton-cornell]

Docs look OK to me :-)

[clayton-cornell]

Looks good. I know the descriptions in the shared content are unlikely to be seen anywhere, but... good habit to be consistent if we can and you never know what search results will show up.