concurrency and transactions about go-agent

[bhcleek]

I should clarify that the lifetime of the goroutines that make the subrequests is always within the lifetime of the goroutine that starts them.

[cmiller01]

This use case would be very helpful for us as well. @bhcleek in our initial testing of the tracing we were passing around the same Transaction within new goroutines, and as the docs point out this didn't really work. It appeared that data was being intermittently dropped.

[peterhellberg]

I would also be interested in knowing more about how to deal with this use-case (multiple goroutines, all with a shorter lifetime than the original goroutine)

If this isn't possible, how about supporting sub-transactions?

[astormnewrelic]

@bhcleek Good eye! Unfortunately, those comments (while a little unclear) are accurate. Without getting too deeply into it, both NewRoundTripper and Transaction weren't explicitly designed with concurrency in mind, and spawning off go routines that access/manipulate the same Transaction can (sometimes) introduce subtle timing/accuracy issues with segments (and possibly other places? )

That said (to echo @cmiller01 and @peterhellberg, thanks both!) better concurrency support would be a pretty sweet feature to have. We're logging/tracking it internally and while we can't promise a delivery date it is on our radar.

We're closing this issue out, but if you still have questions don't hesitate to chime in below or via another one of our support channels.