Uh oh!
There was an error while loading. Please reload this page.
ref(server-utils)!: Replace deprecated db.* span attributes - #23408
Merged
Conversation
Part of the v11 migration away from attributes that `@sentry/conventions` marks deprecated. `db.system` -> `db.system.name`, `db.name` -> `db.namespace`, `db.operation` -> `db.operation.name`, `db.statement` -> `db.query.text` and `db.mongodb.collection` -> `db.collection.name`, across every database integration: Postgres, MySQL, MySQL2, Knex, MongoDB, Mongoose, Redis, ioredis, Tedious, DynamoDB and Supabase. `db.user`, `db.connection_string` and `db.sql.table` are untouched — the first is not deprecated in conventions and the other two are not part of it at all. Sentry's `inferDbSpanData` keys off `db.statement`/`db.system` to name and classify db spans, so every integration was checked to confirm it already sets `name` and `op: 'db'` itself before its old keys were dropped. They all did: that inference only runs in the node SDK, so these integrations had to set both explicitly anyway to be correct on Deno, Bun and Cloudflare. Prisma is the exception and keeps reading the old keys. Its engine emits `db.statement`/`db.system` itself and we only pass them through; the one place the SDK writes rather than reads — the backfill for older Prisma versions that emit no db system at all — now writes `db.system.name`. The `redis.ts` batch/multi span was already on the stable conventions while the command and legacy-client spans were not, so this also makes that file internally consistent. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
msonnb
commented
Aug 13, 2026
MemberAuthor
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 713a95e. Configure here.
msonnb
marked this pull request as ready for review
August 13, 2026 15:06
msonnb
requested review from
JPeer264, logaretm and mydea
and removed request for
a teamAugust 13, 2026 15:06
Contributor
size-limit report 📦
|
logaretm
approved these changes
Aug 13, 2026
Uh oh!
There was an error while loading. Please reload this page.
s1gr1d added a commit
that referenced
this pull request
Aug 24, 2026
Develop landed the same `net.*` -> `server.*`/`network.*` rename for db and messaging spans (#23422), plus a `db.*` rename (#23408) and a restructure of the redis/mysql2/mongoose integrations, so that half of this branch is superseded. Conflicts in `packages/server-utils` and the db/messaging test assertions resolve to develop's version; the orchestrion e2e test apps develop deleted in #23349 stay deleted. `docs/migration/v11-end-state.md` keeps this branch's sectioned layout and `net.*` mapping table with develop's added entries folded in. The branch's own work - the HTTP server and client network attributes in core, node, cloudflare and deno - is unaffected. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
s1gr1d added a commit
that referenced
this pull request
Aug 24, 2026
Develop landed overlapping semantic-convention work (#23408, #23422, #23353, #23405) and restructured the redis integration into `integrations/redis/`. Conflicts were resolved by keeping develop's file layout and layering this branch's attribute changes on top: - ioredis/node-redis spans emit `db.operation.name` and drop `db.connection_string`; `server.address`/`server.port` are only set when known. - The ioredis orchestrion span op moves from `db` to `db.query`, and the connect span to `db` via `SENTRY_OP`, matching the native diagnostics-channel subscriber develop added. - AMQP keeps this branch's removal of the legacy `messaging.*` attributes and adds `messaging.operation.name`. - Test conditionals on the deleted `isOrchestrionEnabled()` helper (#23435) collapse to their channel branch. - `nextjs-16-orchestrion` was deleted upstream (#23349); its ioredis coverage now lives in `nextjs-16/tests/db-page.test.ts`. The v11 migration doc keeps develop's subsection structure with this branch's AMQP and Redis specifics folded in.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
db.system->db.system.namedb.name->db.namespacedb.operation->db.operation.namedb.statement->db.query.textdb.mongodb.collection->db.collection.namepart of #18895