DylanRussell

Hmm we could do it separately.. Proto change doesn't require it. I'm heading out for weekend but can break it out on Monday if you think that's cleaner

Ok I backed off the changes adding support for event name

Once this is submitted I'll make a new PR for those

Created https://github.com/open-telemetry/opentelemetry-python/pull/4652 to add the field to the LogRecord

Yeah good question, same exact issue for the Batch span processor. I'm pretty sure also an issue on the metric processor, [it gets passed through to collect](https://github.com/open-telemetry/opentelemetry-python/blob/main/opentelemetry-sdk/src/opentelemetry/sdk/metrics/_internal/export/__init__.py#L524), and I'm not...

Yeah confirming it's also an issue on the metrics processor. https://github.com/open-telemetry/opentelemetry-python/blob/main/opentelemetry-sdk/src/opentelemetry/sdk/metrics/_internal/export/__init__.py#L476 - it gets set here, and ultimately gets passed all the way into `export` where it gets ignored, for...

https://github.com/open-telemetry/opentelemetry-proto/blob/main/docs/specification.md#otlpgrpc-throttling - this is the section that talks about how to use `RetryInfo`. > To signal backpressure when using gRPC transport, the server MUST return an error with code Unavailable...

i think this can get merged now

Yeah those suggestions SG. I've updated the PR

There's an open PR in go (https://github.com/open-telemetry/opentelemetry-go/pull/6362/files) and a merged PR for Java ([1](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/4ed5a1432f6e8791f5280b4fad32a9ba3fa597a4/gcp-auth-extension/src/main/java/io/opentelemetry/contrib/gcp/auth), [2](https://github.com/open-telemetry/opentelemetry-java/blob/d1ce438e00832f1fb354ce55ec3abdf86abbc28e/exporters/otlp/all/src/main/java/io/opentelemetry/exporter/otlp/http/trace/OtlpHttpSpanExporterBuilder.java#L119-L137)) to support dynamic headers in the OTLP exporter. Meaning the exporter take function(s) that get...