captureException not linking to trace

[ImDevinC]

Summary

When creating a transaction and a trace and then doing sentry.CaptureException(err), the error is not linked to the trace properly.

Steps To Reproduce

func TestTracing(t *testing.T) {
	err := sentry.Init(sentry.ClientOptions{
		Dsn:              os.Getenv("SENTRY_DSN"), // test-project
		Debug:            true,
		TracesSampleRate: 1.0,
		Release:          "development",
	})
	if err != nil {
		t.Error(err)
	}
	ctx := context.Background()
	defer sentry.Flush(2 * time.Second)
	transaction := sentry.StartTransaction(ctx, "TestTracing", sentry.OpName("function"))
	defer transaction.Finish()
	span := transaction.StartChild("function")
	defer span.Finish()
	err = errors.New("this is an error")
	sentry.CaptureException(err)
}

Expected Behavior

When viewing the issue on sentry.io, the exception should have a link to the relevant trace. When viewing the trace, the exception should be shown in the trace view.

Screenshots

Sentry.io Event

Error Event: 120248f44d174a1a8d2a60073153e75a
Trace Event: 7b8eaba5361f4c698e79508fa6af68f4

Environment

SDK

• sentry-go version: v0.15.0
• Go version: 1.19.3
• Using Go Modules? yes

Sentry

• Using hosted Sentry in sentry.io? yes

[cleptric]

Thanks for writing in.
I do confirm that the error event sent to Sentry does indeed not contain the required contexts.trace values to make the link between the transaction and error work.

I'll take a look!

[ImDevinC]

Thanks! Let me know if I can provide any more information to help

[ImDevinC]

For clarification, this seems to work just fine

func TestTracing(t *testing.T) {
	err := sentry.Init(sentry.ClientOptions{
		Dsn:              os.Getenv("SENTRY_DSN"),
		Debug:            true,
		TracesSampleRate: 1.0,
		Release:          "development",
	})
	if err != nil {
		t.Error(err)
	}
	ctx := context.Background()
	defer sentry.Flush(2 * time.Second)
	span := sentry.StartSpan(ctx, "function", sentry.TransactionName("TestTracing"))
	defer span.Finish()
	err = errors.New("this is an error")
	sentry.CaptureException(err)
}

[cleptric]

@ImDevinC I opened a PR to get this fixed. This might take a while to get released, for the moment I suggest using StartSpan instead.