Preview feature feedback: Prisma tracing (`tracing`)

Please share your feedback about the tracing functionality released in v4.2.0 in this issue.

• If you encounter a bug, please open a bug report in this repo.
• If the feature is working well for you, please share this in a comment below or leave a 👍 on this issue.

If you have any questions, don’t hesitate to ask them in the #prisma-client channel in the Prisma Slack.

[alondayan2]

First of all, the new opentelemetry instrumentation is working great for us!

There is just 2 things that bother us:

• Each query creates a lot of spans which pollutes our tracing. An ability to control which span types you get would be awesome.
• The main prisma:engine span doesn’t include the actual sql query that is made, which can be really helpful! + sometimes the queries contain sensitive information, so we need a hook or something similar to determine the final sql query attribute sent with the trace.

Thanks a lot!

[tgensol]

500% agreed with @alondayan2, Could be awesome if we could filter some traces like : "prisma:client:serialize", "prisma:engine:connection", "prisma:client:serialize", "prisma:engine:serialize", "prisma:client:connect" because today, Prisma tracing is 70% of all my traces so my tracing tools (honeycomb/datadog) wend too expensive and I have to remove it.

Like https://www.npmjs.com/package/@opentelemetry/instrumentation-express is doing with ignoreLayersType