DylanRussell
DylanRussell
### Describe your environment _No response_ ### What happened? The [SDK `LoggingHandler`](https://github.com/open-telemetry/opentelemetry-python/blob/b3476a5480efacb58e0dba1ccc4e11f5dbea1a6f/opentelemetry-sdk/src/opentelemetry/sdk/_logs/_internal/__init__.py#L470-L482) can be initialized in a bad state by doing just `handler = LoggingHandler()`. When i do this: ```...
### Is your feature request related to a problem? Related to https://github.com/open-telemetry/opentelemetry-python/issues/4043 and https://github.com/open-telemetry/opentelemetry-python/issues/2284. I would like to update `Exporter.export` to accept a timeout parameter. This way the `BatchProcessor’`s `forceflush`...
### Is your feature request related to a problem? In order to authenticate to some Google APIs, we need the Authorization header to be added and then periodically refreshed in...
### Describe your environment OS: Linux Python version: 3.12 SDK version: 1.24 API version: 1.24 ### What happened? Check out https://github.com/open-telemetry/opentelemetry-proto/issues/640 The response from the HTTP OTLP Exporters should be...
# Description It seems like the behavior we want for `Shutdown()` is: - Don't interrupt an in flight export RPC/Request. - Prevent any new export RPC/Request from being made. -...
It doesn't make sense that we recommend a RetryInfo with time 0, none of the implementations i've seen special case this value, and it goes against the rest of the...
Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4513 I've tried to change the wording such that it's acceptable for SDKs to use gRPC retry config, which only respects the `grpc-retry-pushback-ms` header to handle all backoff /...
# Description Prevent recursive logging issues in `SimpleLogRecordProcessor.on_emit` by inspecting the stack trace to see how many times it's been called. Stop logging when we hit a recursive depth of...
See https://github.com/open-telemetry/opentelemetry-specification/pull/4319. Events API/SDK are deprecated. The logs API/SDK should be used in it's place. An event is just a LogRecord with the `event_name` field set.
We should publicly document which entry_points we load stuff from -- what their names are and what `types` of things we expect the `entry_point` to load in.