Structured log traces do not correlate with any traces collected

[bastiankistner]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/bun

SDK Version

9.22.0

Framework Version

No response

Link to Sentry event

No response

Reproduction Example/SDK Setup

see https://github.com/bastiankistner/sentry-logs-issue

(also tried it with cloudflare worker, but same result)

Steps to Reproduce

see https://github.com/bastiankistner/sentry-logs-issue

Expected Result

Links to traces in logs list should open a trace that actually exists.

Actual Result

Traces for logs cannot be found. For issues captured through captureException however, this works as expected.

[chargome]

Hey @bastiankistner thanks for the repro! @AbhiPrasad could you take a look at this one?

[AbhiPrasad]

Thanks for reporting this @bastiankistner! I've identified what's going wrong here, it's related to how we are accessing the span when capturing logs (we don't select the right active span, so we don't select the right active trace).

We'll try to get this released early next week. I appreciate the reproductions a lot! If you shoot me an email at aprasad + sentry + .io (remove the spaces) we can try to get you some Sentry swag as reward for your help :)

[AbhiPrasad]

Dumping some links to code here so for team meeting on monday for this.

Check-ins (crons) also have broken tracing 😬.

• sentry-javascript/packages/core/src/logs/exports.ts

  Line 105 in 3604a08

  const [, traceContext] = _getTraceInfoFromScope(client, scope);

• sentry-javascript/packages/node/src/sdk/client.ts

  Line 147 in 3604a08

  protected _getTraceInfoFromScope(

• sentry-javascript/packages/core/src/utils/spanOnScope.ts

  Line 29 in 3604a08

  return scope[SCOPE_SPAN_FIELD];

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #16385, which was included in the 9.23.0 release.