Prisma Client always receive engine spans even when not tracing

[millsp]

It looks like the engine always emits spans regardless of whether we send it a traceparent for an operation or not. I think this could cause performance issues if we always emit spans even for users that are not actually using otel?

On the client side, we receive a parent_span_id of 000000000000 when we land in this situation. This came up while testing sampling for the documentation section. An easy way to reproduce this is to use a sampler but set to sample nothing, then see how engine spans are still being emitted. Might be useful to add it as a regression test:

  const provider = new BasicTracerProvider({
    sampler: new TraceIdRatioBasedSampler(0),
    resource: new Resource({
      // we can define some metadata about the trace resource
      [SemanticResourceAttributes.SERVICE_NAME]: "basic-service",
      [SemanticResourceAttributes.SERVICE_VERSION]: "1.0.0",
    }),
  });

_Originally posted by @millsp in https://github.com/prisma/team-orm/issues/150

Potential Solution:
Stop passing undefined as traceId

[garrensmith]

The engine will obey the traceflags settings that are passed to it in the traceparent.
So if the final two fields are 00 it will not emit the spans.
We need something like this:

if (span?.traceFlags === 0 /** if we are tracing */) {
    return `00-${span.traceId}-${span.spanId}-00`
  }

in the getParentSpan.ts file

[millsp]

Thanks, I forgot to update my original comment 🤦