Sentry + Opentelemetry exports at the same time

[nathanscully]

I am in the process of migration Sentry 7 to 8. We already have an existing Open telemetry integration that is pushing traces and metrics to a otel collector, which we are consuming in grafana.
I have managed to migrate this to using the default sentry.init(..) function and can see traces appearing in my sentry console. However I expected having a locally running collector to also receive data. I'd still like to push the otel data to the collector as well as directly to Sentry. It wasn't clear from the docs (that I could find) how to have multiple transports to achieve this?

Any advice?

[AbhiPrasad]

@nathanscully please see: https://docs.sentry.io/platforms/javascript/guides/node/tracing/instrumentation/opentelemetry/#using-a-custom-opentelemetry-setup

[mydea]

FYI we have shipped new docs for this which should make this clearer, hopefully: https://docs.sentry.io/platforms/javascript/guides/node/opentelemetry/custom-setup/ or https://docs.sentry.io/platforms/javascript/guides/node/opentelemetry/using-opentelemetry-apis/#modifying-the-default-opentelemetry-tracerprovider if you only want to send the trace data to a different backend in addition to Sentry.

[sbriceland]

@AbhiPrasad and @mydea - The documentation does not help with the problem mentioned. SentrySampler "rules them all". When span processors are added they still adhere to the behavior of the sampler.

[mydea]

What do you want to achieve? Do you want to send spans to sentry and other places? Or only to other places?

You can use a custom sampler as described here: https://docs.sentry.io/platforms/javascript/guides/node/opentelemetry/custom-setup/#using-a-custom-sampler
But yes, sampling decisions will apply to sending stuff both to Sentry and to other span processors, but this is the expected behavior. I think this is a general OTEL thing that the sampler applies to all span processors?