-
Notifications
You must be signed in to change notification settings - Fork 10
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
Conversation
We want to upgrade the prisma client, but first we need to update the TypeScript dependency to a more recent version. [skip changeset]
328e79b
to
b3db466
Compare
Agent updated in #1174. This is now ready for review. |
✔️ All good! |
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.
b3db466
to
930b3db
Compare
Nice work @tombruijn! |
There was a problem hiding this 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.
This comment has been minimized.
This comment has been minimized.
Fix mistyped named of the library. Co-authored-by: Noemi <[email protected]>
This is a message from the daily scheduled checks. |
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 todb.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
db.query.text
attributes