opentelemetry-python

opentelemetry-python copied to clipboard

> anch is specifically for this task. let's hold thi I say we merge this, this is actually fixing a bug on CI. _Originally posted by @ocelotl in https://github.com/open-telemetry/opentelemetry-python/issues/2818#issuecomment-1183750988_

ocelotl

Run tests in random order

3

Actually, this reminds me that we should run tests in [random order](https://pythonhosted.org/pytest-random-order/). _Originally posted by @ocelotl in https://github.com/open-telemetry/opentelemetry-python/pull/2757#discussion_r896099799_

ocelotl

## Describe your problem This might not be a bug, but not consistent with the specification. :slightly_smiling_face: Creating a named `View` with only `instrument_type` does not raise an Error, even...

pichlermarc

export unclosed span

8

We are using BatchSpanProcessor to batch spans and pushes them to jaeger exporter. We noticed a span is exported only when it ends. However, our system have root span which...

LilyHolms

From the [spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#resolving-duplicate-instrument-registration-conflicts): > If the potential conflict involves instruments that can be distinguished by a supported View selector (e.g., instrument type) a View recipe SHOULD be printed advising the...

ocelotl

From the [spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#resolving-duplicate-instrument-registration-conflicts): > Otherwise (e.g., use of multiple units), the implementation SHOULD pass through the data by reporting both Metric objects.

ocelotl

View should avoid warning if conflict involves multiple description properties

1

From the [spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#resolving-duplicate-instrument-registration-conflicts): > If the potential conflict involves multiple description properties, setting the description through a configured View SHOULD avoid the warning.

ocelotl

Using tracer.start_as_current_span() manually without 'with' context manager leads to error

1

I have a situation where I can't use the usual `with tracer.start_as_current_span("foo") as span:` construct. So instead, I'd like to manually handle calling `__enter__()` and `__exit__()` myself. However, when I...

hashcutdev

OTLPMetricExporter fails to send more than 4MB of data

12

**Describe your environment** Python 3.6.8 Opentelemetry Python 1.12.0 Opentelemetry Collector 0.38.0 **Steps to reproduce** Metrics SDK with quite a few observables generating more than 4MB of data (datapoints) **What is...

overmeulen

Test that metrics methods can be called concurrently

1

_Originally posted by @codeboten in https://github.com/open-telemetry/opentelemetry-python/pull/1887#discussion_r710558412_ [This](https://gist.github.com/mRcfps/0af4f1cb29ffe27cf3aa05d542ac742a) may help.

ocelotl