We are working on a new set of instrumentations using the new Events API, one of which is to emit ResourceTiming events for the resources loaded (#2152), and another to emit PageView event (open-telemetry/opentelemetry-sandbox-web-js#81). As part of this effort, I envision an instrumentation to emit a standalone documentFetch span. We have not created an issue yet to track this as this hasn't been discussed much in the Client SIG.

For your use-case does it work if you configure a custom sampler to drop these spans?

We are working on a new set of instrumentations using the new Events API, one of which is to emit ResourceTiming events for the resources loaded (#2152), and another to emit PageView event (open-telemetry/opentelemetry-sandbox-web-js#81). As part of this effort, I envision an instrumentation to emit a standalone documentFetch span. We have not created an issue yet to track this as this hasn't been discussed much in the Client SIG.

For your use-case does it work if you configure a custom sampler to drop these spans?

@scheler thanks for the status update and a workaround! I think that could be sufficient. Do you know of a sampler that could be a good starting point? I have not done one of those before.

@longility something like this -

const provider = new WebTracerProvider({
  resource,
  sampler: {
    shouldSample: (context, traceId, spanName, spanKind, attributes, links) => {
      return spanName == 'resourceFetch' ? SamplingDecision.NOT_RECORD : SamplingDecision.RECORD_AND_SAMPLED;
    }
  }
});

@longility can you close this issue if the workaround works for you?