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
I made a small repo https://github.com/pksorensen/nextjs-repro-otel/tree/bugs/batchprocessor related to another issue and found additional issues that i am unsure where to report/solve.
I found out that when using batchprocessor is used over simpleprocesor , then no spans are exported when it is on the edge runtime (was testing opentelemetry from Middleware ).
in instrumentation try to change from batch to simple and it works as expected (you see spans in console) and with batch you dont.
The text was updated successfully, but these errors were encountered:
I don't believe this is an issue with this library, as I had issues with BatchSpanProcessor before I even tried using this. From what I can tell, the implementation of that processor is a little buggy. You might have better luck reporting this on the main OpenTelemetry repo for JavaScript. BatchSpanProcessor isn't something Vercel implemented or probably even maintains.
Hi,
I made a small repo
https://github.com/pksorensen/nextjs-repro-otel/tree/bugs/batchprocessor
related to another issue and found additional issues that i am unsure where to report/solve.vercel/next.js#67737
I found out that when using batchprocessor is used over simpleprocesor , then no spans are exported when it is on the edge runtime (was testing opentelemetry from Middleware ).
in instrumentation try to change from batch to simple and it works as expected (you see spans in console) and with batch you dont.
The text was updated successfully, but these errors were encountered: