Zach Montoya

@cijothomas please let me know if this belongs in a separate issue, but I've found a somewhat related issue where the route pattern is missing when the action uses [conventional...

Hi @nblumhardt , thanks for the bump 😄 The fix in `dd-trace-dotnet` has been good and we haven't had any reported issues since, so I've ported the fix in #1584....

Hey Pierre, there's a couple more files that need to be updated with the revised application paths: - [x] `tracer/build/_build/Build.GitHub.cs` - [x] `tracer/build/_build/PrepareRelease/SetAllVersions.cs`

Hi @bluetentacle , thank you for the detailed report. We are having internal discussions on how to better represent services across Datadog, but we do not yet have any timelines...

I ended up updating the RabbitMQ samples in my interface integration PR: https://github.com/DataDog/dd-trace-dotnet/pull/3256 I can rebase this PR once that is merged

> Questions: > * Now that we have ASM, do we need to tie that into this WCF obfuscation somehow? Thinking on this more, I think this PR and the...

Is it feasible to add an automated test for this or will we rely on manual testing inside AWS to validate?

Hi @fjmorel thank you for the detailed report. In your situation it looks like some of the method you're trying to instrument are _extension methods_. Extension methods compile down to...

Ah I think I've found the issue: the `Either` and `EitherAsync` types you are trying to instrument are generic structs and we currently do not support that scenario, hence why...

> - if trace is dropped because of high volumes, then the work of obfuscation is not done After investigating the trace serialization pipeline, this is unfortunately not true. Assuming...