Perfect. This is very helpful and paints a very clear picture. Thank you for taking the time to create this issue. Would you have any interest in doing the work? Otherwise we can schedule some work internally.

I might be able to find time to do this assuming it's as simple as creating the span in before instead of after.

I think it should be much easier than that. No need to move it to before. Wouldn't this work?

Replacing:

span, _ := tracer.StartSpanFromContext(ctx, operationName, opts...)

With:

var span ddtrace.Span
span, db.Statement.Context = tracer.StartSpanFromContext(ctx, operationName, opts...)

But I see what you mean. Never mind the above :) Perhaps we could store the span in the context, just like we do the start time now... I wonder if there's any risk to create a leak like that, considering someone never triggers the after...

I'm pretty sure this is impossible without rewriting Gorm? Since Gorm doesn't call ExecContext, or QueryContext, the context won't even be passed to link the two. I'm not sure how you do this. I imagine this is why Begin/Commit does show up tied to the parent spans - because Gorm calls BeginTx(ctx...)

Gorm uses these interfaces:

// SQLCommon is the minimal database connection functionality gorm requires.  Implemented by *sql.DB.
type SQLCommon interface {
	Exec(query string, args ...interface{}) (sql.Result, error)
	Prepare(query string) (*sql.Stmt, error)
	Query(query string, args ...interface{}) (*sql.Rows, error)
	QueryRow(query string, args ...interface{}) *sql.Row
}

type sqlDb interface {
	Begin() (*sql.Tx, error)
	BeginTx(ctx context.Context, opts *sql.TxOptions) (*sql.Tx, error)
}

type sqlTx interface {
	Commit() error
	Rollback() error
}

I guess that's what I see in my traces - only Begin/Commit show up associated, all others are their own root spans (which is really really annoying)

Any progress or updates on this? i am facing same issue. If required i can help with the PR.

Hi, @prasad-marne. We have not made any progress on this issue and any community help is welcome.

Hey -- wondering if there's any update on this? Have other people found it a blocker from using? I want to upgrade from Gorm 1.0 to 2.0 but need to make sure the gorm2 wrapper for ddtrace is usable

Any updates on this issue? looks like it has not been addressed on the latest release of contrib/gorm.io/gorm.v1

I don't know if it's related, but recently we updated gorm from v1 to v2 and used this example to help us to configure datadog with gorm #759. But the traces from the http and gorm database traces are not correlated and they are shown as separated traces as I show in the capture images.

So, searching for possible workarounds, I found this issue in the gorm repository: go-gorm/gorm#1231

And use the function WithContext(ctx) to propagate the context. With this approach, the full trace is shown in DataDog panel.

Could it be possible that DataDog cannot get the context?

@ervitis
I'm currently encountering the same problem where I can't see the correlated traces between Gin and Gorm. They seem to be separated. However, the issue lies in the fact that I can see the Gorm tracing and the Gin tracing have their own root spans. On the other hand, the Gin Context doesn't seem to carry the right information. In my case, I passed the Gin Context from the handler to the repository layer where Gorm executed the query. Once I used db.WithContext(c.Request.Context) instead of the Gin Context, the correct tracing appeared in Datadog.

However, there's still one question remaining: if I want to use a goroutine to perform some asynchronous jobs, should I copy the Gin Context to maintain the information?
Does anyone know how to deal with this?

We also have this issue (among others) with the Gorm tracer. We created a fork and are experimenting with potential fixes. So far we have made pretty good improvements.

main...onfocusio:dd-trace-go:chore/sc-13429/gorm-propagate-parent-span

If this solution sounds good to maintainers, maybe I could allocate some time updating the tests and opening a PR to get this merged into the official repo.