packages/nextjs/src/server/index.ts
quite a few processors in this file:
devErrorSymbolicationEventProcessor: should be able to use ignoreSpans by filtering on attribute. The error symbolication part is not a concern.getGlobalScope().setTag('turbopack', true); we most likely want to set an attribute for this on the segment span (?)client?.on('preprocessEvent' - This one does a lot of data modification. Can likely be ported to processSpan and anothergetGlobalScope().addEventProcessor - this one drops a lot of transactions. The one filtering on transaction names can likely be ported to ignoreSpans, especially the ones that seem to filter out OTel spans from NextJS. The TRANSACTION_ATTR_SHOULD_DROP_TRANSACTIONbehaviour is a bit of an unknown to me but seems like we set this attribute post span-start, so likely not something we can continue to support.
packages/nextjs/src/server/index.tsquite a few processors in this file:
devErrorSymbolicationEventProcessor: should be able to useignoreSpansby filtering on attribute. The error symbolication part is not a concern.getGlobalScope().setTag('turbopack', true);we most likely want to set an attribute for this on the segment span (?)client?.on('preprocessEvent'- This one does a lot of data modification. Can likely be ported toprocessSpanand anothergetGlobalScope().addEventProcessor- this one drops a lot of transactions. The one filtering on transaction names can likely be ported toignoreSpans, especially the ones that seem to filter out OTel spans from NextJS. TheTRANSACTION_ATTR_SHOULD_DROP_TRANSACTIONbehaviour is a bit of an unknown to me but seems like we set this attribute post span-start, so likely not something we can continue to support.