Alex Boten
Alex Boten
Currently the list of distributions only link to the contents of the directories. It would be useful to describe the intent of each distribution.
Adding the ability to set a MeterProvider to `otelgrpc` instrumentation for future use.
As per the output available [here](https://github.com/open-telemetry/opentelemetry-go-contrib/runs/3874070980?check_suite_focus=true), a flaky test was causing CI failures with the following message: ``` === RUN TestInterceptors/StreamClientSpans grpc_test.go:181: Error Trace: grpc_test.go:181 grpc_test.go:106 Error: "[%!s(*trace.snapshot=&{grpc.testing.TestService/StreamingInputCall {[155 73...
The spec says there are 4 data points: 1. Sum 2. Gauge 3. Histogram 4. Exponential Histogram Currently the SDK only implements 3 of them: Sum, Gauge, Histogram. See: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/datamodel.md#opentelemetry-protocol-data-model
As per the SDK specification: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#exemplar
As per the following comment: wondering if this were to return metric sequence you could simplify this chain of calls `callback` -> `_receive_metrics` -> `add_metrics_data` -> `deque` -> `yield`. _Originally...
The spec describes environment variables that should be supported to configure the log level, this feature request is to add support in the current implementation. https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/sdk-environment-variables.md
As documented in PR https://github.com/open-telemetry/opentelemetry-python/pull/1925, there are several manual steps in releasing a hotfix. This should be made easier for maintainers via github actions.
As with the other signals, metrics should be available for export as OTLP over HTTP.