-
Notifications
You must be signed in to change notification settings - Fork 10
Support encoding optional headers in the OTLP-Arrow exporter #35
Conversation
… testbed authors)
…lues from client.Info.Metadata
The exporter has been updated with a new configuration struct named |
@ptal especially @paivagustavo, thanks! |
PTAL. I have updated the exporter to locate the Auth extension and use its PerRPCCredentials().GetRequestMetadata() to get per-request headers. All the existing mechanisms work at the stream level, and I will update the Receiver PR to correctly merge the incoming context (from the stream) w/ the per-request metadata (from the arrow batch). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for taking a look at the auth extensions.
…ollector into jmacd/exp_hpack
Description:
This exports the result returned by the Auth extensions'
credentials.PerRPCCredentials
interface if present and exports it with the Arrow batch using the new optional bytes field added here: f5/otel-arrow-adapter#85. This matches the behavior of the Receiver in #34. The problem about Auth is described in open-telemetry/opentelemetry-collector#6965.Unrelated cleanup. While working on the testbed, I noticed it is helpful if the Settings type is exported, not an internal package. This moves the ArrowSettings up two levels.
Part of #33