Replies: 2 comments 6 replies
-
|
@jinsley8 we should have fixed this in the latest SDK release. Please upgrade your SDK to |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
@AbhiPrasad No dice, I upgraded to v8.80, deleted I still get these errors: I can provide stack trace if needed. |
Beta Was this translation helpful? Give feedback.
-
|
shoot - sorry for the trouble! If you run It looks like that prisma optimize doesn't expose how they use OpenTelemetry in anyway, so I don't think we'll have a good time overriding this 😬. |
Beta Was this translation helpful? Give feedback.
-
|
Here is the output: This is how I initialize Prisma import { PrismaClient } from '@prisma/client';
import { withOptimize } from '@prisma/extension-optimize';
const globalForPrisma = global as unknown as { prisma: PrismaClient };
export const prisma =
// eslint-disable-next-line @typescript-eslint/no-unnecessary-condition
globalForPrisma.prisma ||
new PrismaClient({
log: process.env.NODE_ENV === 'development' ? ['query', 'error', 'warn'] : ['error'],
errorFormat: 'pretty',
}).$extends(withOptimize());
if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = prisma;
export default prisma;If I use the same example from the Prisma instructions I get the same error: import { PrismaClient } from '@prisma/client';
import { withOptimize } from '@prisma/extension-optimize';
const prisma = new PrismaClient().$extends(withOptimize());
export default prisma; |
Beta Was this translation helpful? Give feedback.
-
|
I'm digging through the source code of
There is no way to configure the OTel instance that I've reached out to Prisma folks that I am in contact with to see if we can get this solved! Otherwise I just think |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your help looking into this. I will disable Optimize for now if that is the case. I'll keep an eye on upcoming Prisma releases too to see if they address it. I'll open an issue on the Prisma repo this week. |
Beta Was this translation helpful? Give feedback.
-
|
The same issue happens when running Application Insights (https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/monitor/monitor-opentelemetry/) and Sentry at the same time. We are using Error: |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
@lapa182 could you open a separate GitHub issue? We can take a look! |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I upgraded to
"@sentry/nextjs": "^8.0.0"with"next": "14.2.3"pages router and new@prisma/extension-optimizeextensionI get Sentry Logger errors when my
instrumentation.tsfile is setup like the example below:Any idea what could be triggering these sentry errors? It looks there is a conflict with both
@sentry/nextjsand@prisma/extension-optimizeusing@opentelemetry/apiAPI.I've opened a discussion with Prisma as well 24213
Beta Was this translation helpful? Give feedback.
All reactions