Sean Marciniak
Sean Marciniak
This needs to be added to the main project, the otel contribution written by me is currently flawed since sarama does validation checks on the auth mechanism used. This should...
Could I ask you to rebase this PR @nabam ?
> I am not sure if this can be achieved but if we did the `keyBy` option and allow us to use things like the `traceId`, `spanId` and/or the `service.name`,...
> My thoughts here were to add an OTTL expression as part of the component config in order to point at the proper field to key off of. I have...
Unfortunately, it looks like it was missed in the backlog of PRs. If you'd still like this feature in, please reopen and rebase with main.
From Atlassian's experience, we've not needed the ballast extension for a deployment that is strictly observing the host (doesn't expose any endpoints for services to send data, and prom is...
> @povilasv @MovieStoreGuy What do you think about this? I would like to stay consistent with the OTLP receiver, which does: > > ```yaml > receivers: > otlp: > protocols:...
Is it worth converting this PR to draft until it is ready for review?
I've parked the additional actions, I would like to follow up on those to be done within the transport instead of within the encoding step.
No worries, I don't have much bandwidth to work on this now but I would love to pick this up at some point.