Marco Schaefer

> I updated packages, but unfortunately this doesn't fix our issue 😢 Oh no, had a slight hope that not closing he connection caused the issue. The [otel spec for...

Heads up since you are using the otlp-http-transport, we are going to release a new Faro version with updated otel dependencies. We aligned semantic attributes with the current otel spec....

Hi @mxab I tested it in the Faro demo. But I think there's an issue because I got another ask recently because of an undefined context. Screenshot from the demo.

@mxab When and were do you initialize Faro? Do you maybe have something else running which initializes otel? Maybe you can share your Faro config?

> But if I debug it in the browser the otel.trace.getSpanContext(otel.context.active()) returns an undefined context getSpanConext is fetching the context with this line of code: `const ctx = otel?.trace.getSpanContext(otel.context.active());` If...

Thank you so much Max 🙏 Please don't hesitate to ask or when you want to validate assumptions. You can also find ob the Faro community Slack Hmm ok, with...

Maybe an idea: I see that the [initOtel(trace, context))](https://github.com/grafana/faro-web-sdk/blob/c5697874f90035bf14446bd9fd0a91c9c608b642/packages/core/src/api/traces/initialize.ts#L20) function in faro core doesn't validate the inputs. Maybe it happens that it gets called multiple times and overwrites the context...

Did you already try the otel logger? Right before calling the Faro init function you can enable otel logging. ``` import { diag, DiagConsoleLogger, DiagLogLevel } from '@opentelemetry/api'; // ......

You should see them in the browsers console, no?

Hey @mxab no worries at all and many thanks for the update :) Glad it's working now. Thanks for opening the issue and making Faro better. Please keep asking and...