👋 🧭 📐 Any thoughts on telemetry or tracing Prisma database to help with optimization? There’s this ticket https://github.com/prisma/prisma/issues/5956 but I haven’t seen any updates in a while. We’re having trouble specifically using Datadog as a telemetry sink, tying queries made in a serverless context hosted on Vercel with a NextJS app. Any help or insight would be appreciated! /cc @Matt Mueller (Prisma Client PM) 🙏

Hey @ed! We're actively working on it. Mind if I ping you to try out an early version when it's available?

Absolutely! Would def help test things out and provide feedback. What form would you imagine this taking? Middleware implementing some kind of OpenTelemetry or configurable via a transport? Curious to hear how we might plan for this with the rest of our telemetry stack.

Right now we're assuming your existing application is setup to use OpenTelemetry and send events to a tracing backend like DataDog. We plan to pull in this configuration (from a global context) and then send events through it. So it should be zero config from your end, if it's setup the way we expect. Your application will be a good test to see how flexible this is though. This issue should provide an overview of where things are at: https://github.com/prisma/prisma/issues/9601 Given the holiday hours, I think we're still a couple weeks out, but I'll ping you when we have something to share.

Thanks @Matt Mueller (Prisma Client PM) - Appreciate the heads up. I’ll look into implementing this during the next couple weeks and get back to you with how it goes.