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
Most beginners will be more familiar with @opentelemetry/sdk-node as OpenTelemetry's JavaScript getting started guide uses it.
Currently Prisma documentation on enabling OpenTelemetry tracing describes only how to make use of the first approach. Showing how to make it work with new NodeSDK({ /* ... */ }) would make it easier to enable tracing in Prisma.
Suggested solution
Expand the documentation page to also mention how to use it with @opentelemetry/sdk-node.
Additional context
I got really confused when trying to enable tracing in Prisma following the documentation mentioned above after having configured basic instrumentation based on OpenTelemetry's JavaScript getting started guide (also mentioned above).
The text was updated successfully, but these errors were encountered:
Yes, got it working with a very similar setup 👍 Something similar should probably end up in the documentation (either with traceExporter as you've shown or also with spanProcessor, but not sure if that wouldn't complicate the example too much).
Problem
As far as I understand there are two ways of configuring OpenTelemetry in JavaScript (source):
Most beginners will be more familiar with
@opentelemetry/sdk-node
as OpenTelemetry's JavaScript getting started guide uses it.Currently Prisma documentation on enabling OpenTelemetry tracing describes only how to make use of the first approach. Showing how to make it work with
new NodeSDK({ /* ... */ })
would make it easier to enable tracing in Prisma.Suggested solution
Expand the documentation page to also mention how to use it with
@opentelemetry/sdk-node
.Additional context
I got really confused when trying to enable tracing in Prisma following the documentation mentioned above after having configured basic instrumentation based on OpenTelemetry's JavaScript getting started guide (also mentioned above).
The text was updated successfully, but these errors were encountered: