Wrong `db.system` as per OTeL naming convention

[fmiqbal]

How do you use Sentry?

Self-hosted / on-premises

SDK version

4.20.0

Laravel version

12.41.1

Steps to reproduce

1. Use postgresql as database
2. Enable performance tracing
3. Make a few call

Expected result

1. in /insights/backend/database/ in Sentry Self Hosted version 25.11.1 (its from Insight -> Backend -> Queries)
2. The table is filled correctly

Actual result

2. Observe the Queries Per Minute and Average Duration graph is working, but empty table
3. Observe in the actual span, the tag for db.system is pgsql

I am a bit curious because on my instance (in k8s) it didnt show, digging a bit deeper I suspect its because of

sentry-laravel/src/Sentry/Laravel/Tracing/EventHandler.php

Line 177 in 95f2542

'db.system' => $query->connection->getDriverName(),

Meanwhile sentry use (as stated in the docs) https://docs.sentry.io/product/insights/backend/queries/#span-eligibility, which I think it use https://github.com/open-telemetry/semantic-conventions/blob/main/docs/db/database-spans.md, which doesnt have pgsql and that's why its not working on self-hosted,

Also this is working in sentry.io, But I don't know if I should raise there too,

For the time being I am trying to spun up fresh instance of sentry and try that first

[linear]

LARAVEL-50

[Litarnus]

Hi @fmiqbal! Thanks for pointing that out.

If I understand it correctly it should work when we just map it to postgresql. I will test it and then come back to you

[fmiqbal]

Yes, that's what I also check, but turns out there's un underlying issue of span.system filter, as I cross-reference the issue, but I think changing to postgresql is also the right move to be more aligned with what sentry expect

But I still have problem on mssql (trying to change the db.system to microsoft.sql_server as per Otel spec), because it turns out, its still issue, because sentry.py currently only support sqlite, postgresql, mariadb, mysql, and oracle as seen here

https://github.com/getsentry/sentry-python/blob/master/sentry_sdk/integrations/sqlalchemy.py#L125

And that will become a problem because if the upstream issue of span.system is fixed, the UI will force to filter on span.system which wont have MSSQL, but that is the issue on upstream