You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No SocketIO Prisma database queries being captured
Description
We are using the most update-to-date New Relic agent and it is capturing database queries now from Prisma (THANK YOU!) but only for queries executed from code within our HTTP endpoints. Any queries executed from code sourced from our persistent web socket connections do not appear to be tracked. NOTE: We are running on top of FeathersJS / Prisma. Why?
Nothing to output (since NR isn't capturing anything 😉 )
Steps to Reproduce
Install FeathersJS / Prisma alongside NR agent and set up two connections (HTTPS endpoint vs Socket IO connection). Execute a query in both. Socket IO connection queries don't get captured.
No SocketIO Prisma database queries being captured
Description
We are using the most update-to-date New Relic agent and it is capturing database queries now from Prisma (THANK YOU!) but only for queries executed from code within our HTTP endpoints. Any queries executed from code sourced from our persistent web socket connections do not appear to be tracked. NOTE: We are running on top of FeathersJS / Prisma. Why?
See original request here for more information.
https://forum.newrelic.com/s/hubtopic/aAX8W0000008f99WAA/new-relic-nodejs-agent-now-instruments-prisma?t=1686310540023
Expected Behavior
All Prisma database queries should be captured from Prisma regardless of where they're sourced from (HTTP endpoint or web socket connection)
Troubleshooting or NR Diag results
Nothing to output (since NR isn't capturing anything 😉 )
Steps to Reproduce
Install FeathersJS / Prisma alongside NR agent and set up two connections (HTTPS endpoint vs Socket IO connection). Execute a query in both. Socket IO connection queries don't get captured.
Your Environment
Additional context
Can't think of anything
The text was updated successfully, but these errors were encountered: