Skip to content

fix(node): Ensure prisma integration creates valid DB spans #11908

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

Merged
merged 2 commits into from
May 6, 2024

Conversation

mydea
Copy link
Member

@mydea mydea commented May 6, 2024

Closes #11891

@mydea mydea requested review from lforst and s1gr1d May 6, 2024 08:14
@mydea mydea self-assigned this May 6, 2024
@@ -13,6 +13,19 @@ const _prismaIntegration = (() => {
new prismaInstrumentation.PrismaInstrumentation({}),
);
},

setup(client) {
client.on('spanStart', span => {
Copy link
Member Author

Choose a reason for hiding this comment

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

Sadly we have no hook in the integration for this, but I think this is OK - as this integration is opt-in anyhow (as of now, at least), there is no overhead if not using this.

Copy link
Member Author

Choose a reason for hiding this comment

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

Possible improvement for this: We could PR this upstream to have a proper hook for this...

@mydea mydea merged commit 782756b into develop May 6, 2024
82 checks passed
@mydea mydea deleted the fn/prisma-spans branch May 6, 2024 09:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rewrite Prisma spans to ensure they populate Queries Insights in Sentry
2 participants