Felix Geisendörfer

PR for git workaround is ready: https://github.com/DataDog/dd-trace-go/pull/811

@pellared thanks for the link. It seems like they have separate `go.mod` files for some, but not all, sub-directories. I'll dig into this some more later, but the approach seems...

@marcind sorry you're hitting this issue. I think it's reasonable to expect that upgrading `dd-trace-go` doesn't break your application. That being said, it's a tricky situation. glog seems difficult to...

@prithvihv Sorry for the late reply and the issue you're experiencing. Would it be possible for you (or @eleboucher) to share the pprof file for this? You can send it...

@eleboucher thanks, I received the data! All profiles were generated while applying the same workload? > Edit: your workaround doesn't impact the memory Looking at your data, I'm not surprised...

@eleboucher I followed up with our support team and they should reach out to your shortly. But the gist is that tracing long-running transactions with many queries will create a...

Thanks for the proposal @aidansteele. I'll leave it to team @DataDog/tracing-go to comment, but feel free to ping me if this gets stuck for some reason.

@Julio-Guerra and myself had a lot of discussions about dynamic instrumentation in the past and have explored a few directions. Right now there are not concrete plans, but I'd be...

Pixie and dynamic instrumentation in general is awesome. But it's a tradeoff. Advantages: - Dynamically add instrumentation (logging, tracing, ...) without recompiling. - Avoid polluting your app code with instrumentation...

@gbbr @knusbaum this is just an idea for making the local dev experience better until we have a proper solution to the issue. The reason I'm submitting this is because...