This message was deleted.

@User Which database are you using in your application?

I'm using Postgres. I see there is a psycopg2 opentelemetry package but it doesn't seem to work. I ensured opentelemetry-instrumentation-psycopg2 was installed.

do you use psycopg2 to connect with postgres from python?

I let Django ORM set this, but it internally uses psycopg2 https://docs.djangoproject.com/en/4.0/ref/databases/#postgresql-notes

I see. can you share your requirements.txt for this app? Will have to check this if Django ORM is supported

Django 4.0.2 opentelemetry-api 1.9.1 opentelemetry-distro 0.28b1 opentelemetry-exporter-otlp 1.9.1 opentelemetry-exporter-otlp-proto-grpc 1.9.1 opentelemetry-exporter-otlp-proto-http 1.9.1 opentelemetry-instrumentation 0.28b1 opentelemetry-instrumentation-dbapi 0.28b1 opentelemetry-instrumentation-django 0.28b1 opentelemetry-instrumentation-psycopg2 0.28b1 opentelemetry-instrumentation-wsgi 0.28b1 opentelemetry-propagator-jaeger 1.9.1 opentelemetry-proto 1.9.1 opentelemetry-sdk 1.9.1 opentelemetry-semantic-conventions 0.28b1 opentelemetry-util-http 0.28b1 psycopg2-binary 2.9.3

Can you use

psycopg2

instead of

psycopg2-binary

the later is non-production setup and is not supported by otel instrumentation? If you use postgres/ mysql/ sqlite3 as engine in django ORM, you should be able to see data

ah that was it, thank you!

are you able to see DB call data now?

Yes I am

nice 🙌

Glad you were able to figure this out. The reason we don't support the

psycopg2-binary

is that the official docs don't recommend it for the production use and we don't want to add instrumentation for the non-production ready libs. https://www.psycopg.org/docs/install.html#psycopg-vs-psycopg-binary