Riccardo Magliocchetti comments

Results 338 comments of


                                            Riccardo Magliocchetti

aiokafka instrumentation

Fix merged and released, closing.

auto_instrumentation.initialize() leads to a flurry of ModuleNotFoundError errors when traceloop-sdk is present

@obs-gh-abhishekrao There's no such thing of "its own scope of modules to auto-instrument", instrumentations declare entry-points we use to discover them. If they define these entry points we try to...

Add optional traceback as spanattribute for psycopg2 instrumentation

I understand the issue but it doesn't feel right to to add something ad-hoc per instrumentation

flaky test for opentelemetry-sdk in CI

> I guess this issue can be closed? Indeed, thanks!

Add NoOpTracerProvider test for starlette

@mspillane please sign the CLA

Import the GCP resource detector class

Why are we taking the burden of maintaining an empty package upstream just for a re-export? Why not defining the entry point in your package so that people interested can...

Import the GCP resource detector class

> I'm not sure how the versioning of this package would work.. Do we just keep the version forever pinned at 0.1 ? Do we have to bump the version...

Instrument HttpResponse body stream.

Have seen this just now but I've implemented more or less what you did. I think we should take a look at using getvalue() instead of read() as it should...

Introducing tox-uv

![8wgjxj](https://github.com/open-telemetry/opentelemetry-python-contrib/assets/12932/90cea392-433a-42a9-998c-fb81d1de905f)

fix(tornado): ensure reading future.result() won't throw an exception in client.py _finish_tracing_callback

@jgibo Have you taken a look on how the asyncio instrumentation handles things?