Describe the bug
We upgraded Datadog.Trace.Bundle from 2.59.0 to 3.3.1 and no longer have custom traces in Datadog. Automatic traces still are working, i.e. ASP.NET Core Requests.
To Reproduce / Runtime environment
Steps to reproduce the behavior:
- Azure Container App
- Linux Docker image:
FROM mcr.microsoft.com/dotnet/aspnet:8.0
- Datadog serverless-init:
1.2.8
- NuGet:
Datadog.Trace.Bundle 3.3.1
- In code: invoke
Datadog.Trace.Tracer.Instance.StartActive to create custom traces.
Expected behavior
Expecting to still have custom traces in addition to automatic traces. Downgrading to 2.59.0 immediately resolved the issue.
Additional context
Nothing in the v2 to v3 migration guide seemed to point to the issue. Wondering if the serverless-init is somehow not compatible with the latest NuGet package.
Describe the bug
We upgraded
Datadog.Trace.Bundlefrom2.59.0to3.3.1and no longer have custom traces in Datadog. Automatic traces still are working, i.e. ASP.NET Core Requests.To Reproduce / Runtime environment
Steps to reproduce the behavior:
FROM mcr.microsoft.com/dotnet/aspnet:8.01.2.8Datadog.Trace.Bundle 3.3.1Datadog.Trace.Tracer.Instance.StartActiveto create custom traces.Expected behavior
Expecting to still have custom traces in addition to automatic traces. Downgrading to
2.59.0immediately resolved the issue.Additional context
Nothing in the v2 to v3 migration guide seemed to point to the issue. Wondering if the
serverless-initis somehow not compatible with the latest NuGet package.