Add query source to DB spans

[antonpirker]

Adding OTel compatible information to database spans that show the code location of the query.
Refs getsentry/team-sdks#40

This has to be

• "opt in" and
• only add the location where the query takes longer than 100ms to run
• working with SQLAlchemy
• working with Django
• working with asyncpg

Documentation PR: getsentry/sentry-docs#8558

In the product this will then be displayed with something like this:

[AbhiPrasad]

Is it possible to tell what the overhead of this is going to be?

[antonpirker]

Is it possible to tell what the overhead of this is going to be?

Hard to tell. I am "only" walking the stack until i find the right frame and then add the data to the span. But maybe we should do some load testing.

(it is opt-in, so we will not break anything out of the box)

[antonpirker]

@AbhiPrasad Did some load testing on an FastAPI example app running 50 concurrent users doing around 85 requests per second:

Without attaching the query source:

With attaching the query source:

The only difference I can see is the 99percentile is a bit slower with attaching query sources (but those are probably some outliers, the the max column)

So I think we are good here.

[antonpirker]

Here is an example transaction with query source:
https://sentry-sdks.sentry.io/performance/fastapi:19ad8dc0db9548c6bb91e67df441eafb/?project=6618415&query=http.method%3AGET&referrer=performance-transaction-summary&showTransactions=recent&statsPeriod=1h&transaction=%2Fapi%2Fshows%2F%7Bshow_id%7D&unselectedSeries=p100%28%29&unselectedSeries=avg%28%29

[antonpirker]

And here the event as JSON: python-with-query-source.json

[antonpirker]

One thing to mention: When finding the right frame to attach as query source I am omitting external sources (stuff that is in site-packages and dist-packages)

This works well if someone has for example Django and does queries using Djangos ORM because the queries are done in the users code. But if they have Django and DjangoRestFramework the place in the users code that defines the query does not show up in the stack trace and I can not add the query source.

Which is a bummer, but I think kind of ok, because if they have DjangoRestFramework the transaction name will lead them to their serializer and then they know where to look for the query/queries.

[sentrivana]

LGTM, left some suggestions