Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update prism instrumentation #1172

Merged
merged 3 commits into from
Feb 25, 2025
Merged

Update prism instrumentation #1172

merged 3 commits into from
Feb 25, 2025

Conversation

tombruijn
Copy link
Member

@tombruijn tombruijn commented Feb 19, 2025

Update TypeScript to version 5.7.x

We want to upgrade the prisma client, but first we need to update the TypeScript dependency to a more recent version.

Update Prism to 6.4 and test apps

Update test apps to match the new trace structure by updating the span names and attributes.

OpenTelemetry changed the db.statement span attribute to db.query.text in newer versions of their Semantic Conventions, so we'll need to update the attributes we sanitize in the extension/agent to match.

To do

  • Update agent to sanitize db.query.text attributes

@tombruijn tombruijn self-assigned this Feb 19, 2025
@tombruijn tombruijn marked this pull request as draft February 19, 2025 20:31
We want to upgrade the prisma client, but first we need to update
the TypeScript dependency to a more recent version.

[skip changeset]
@tombruijn tombruijn force-pushed the update-prism-instrumentation branch from 328e79b to b3db466 Compare February 20, 2025 11:39
@tombruijn
Copy link
Member Author

Agent updated in #1174. This is now ready for review.

@tombruijn tombruijn marked this pull request as ready for review February 20, 2025 11:39
@backlog-helper
Copy link

backlog-helper bot commented Feb 20, 2025

✔️ All good!

New issue guide | Backlog management | Rules | Feedback

Update test apps to match the new trace structure by updating the span
names and attributes.

OpenTelemetry changed the `db.statement` span attribute to
`db.query.text` in newer versions of their Semantic Conventions, so
we'll need to update the attributes we sanitize in the extension/agent
to match.
@tombruijn tombruijn force-pushed the update-prism-instrumentation branch from b3db466 to 930b3db Compare February 20, 2025 11:42
@DannyAziz
Copy link

Nice work @tombruijn!

Copy link
Contributor

@unflxw unflxw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change itself seems okay. I'm unsure if this will break for users of older Prisma versions, and what we should do in that case.

If there's no good solution, maybe we need to consider removing automatic support for Prisma (so it's no longer our dependency) and changing the docs to ask customers to bring their own @prisma/instrumentation version and throw it at the additionalInstrumentations config option.

@backlog-helper

This comment has been minimized.

Fix mistyped named of the library.

Co-authored-by: Noemi <[email protected]>
@backlog-helper
Copy link


This is a message from the daily scheduled checks.

New issue guide | Backlog management | Rules | Feedback

@tombruijn tombruijn merged commit 7191d09 into main Feb 25, 2025
29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants