[BUG]: Trace data not sent to CI Visibility

[thausercelonis]

Tracer Version(s)

3.11.1

Operating system and platform

Windows (x64), Ubuntu-latest (Github Agent)

Instrumentation Mode

manual with nuget package

TFM

net8.0

Bug Report

We have very custom benchmarks. It is not really a unit test, not a real benchmark. The results should be written to Datadog CI Visibility. To leverage that we are using the Datadog.Trace package. The reproduction code (separate code example) I will post here, too. Problems:

• Nothing is written to Datadog, not in agent mode, not in agentless mode.
• Nothing will be written to debug, not if you write to file, not to console.
• No error
• No exception

There is real nothing, what you can use to get an idea, what the problem could be.

Reproduction Code

    static void Main()
    {
        Environment.SetEnvironmentVariable("DD_TRACE_DEBUG", "true");
        Environment.SetEnvironmentVariable("DD_TRACE_LOG_FILE", "dd-trace.log");
        //Environment.SetEnvironmentVariable("DD_TRACE_LOG_FILE", "console");
        Environment.SetEnvironmentVariable("DD_TRACE_STARTUP_LOGS", "true");

        Environment.SetEnvironmentVariable("DD_CIVISIBILITY_AGENTLESS_ENABLED", "true");
        Environment.SetEnvironmentVariable("DD_API_KEY", "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx");
        Environment.SetEnvironmentVariable("DD_SITE", "datadoghq.com");
        Environment.SetEnvironmentVariable("DD_ENV", "ci");
        Environment.SetEnvironmentVariable("DD_SERVICE", "my-test-service");

        Console.WriteLine("Datadog Environment Variables Set!");

        Console.WriteLine("Checking Environment Variables:");
        Console.WriteLine($"DD_SERVICE: {Environment.GetEnvironmentVariable("DD_SERVICE")}");
        Console.WriteLine($"DD_ENV: {Environment.GetEnvironmentVariable("DD_ENV")}");
        Console.WriteLine($"DD_API_KEY: {Environment.GetEnvironmentVariable("DD_API_KEY")}");
        Console.WriteLine($"DD_SITE: {Environment.GetEnvironmentVariable("DD_SITE")}");
        Console.WriteLine($"DD_CIVISIBILITY_AGENTLESS_ENABLED: {Environment.GetEnvironmentVariable("DD_CIVISIBILITY_AGENTLESS_ENABLED")}");
        Console.WriteLine($"DD_TRACE_DEBUG: {Environment.GetEnvironmentVariable("DD_TRACE_DEBUG")}");
        Console.WriteLine($"DD_TRACE_LOG_FILE: {Environment.GetEnvironmentVariable("DD_TRACE_LOG_FILE")}");

        var module = TestModule.Create("MyConsoleAppTests");
        var suite = module.GetOrCreateSuite("MyTestSuite");

        var test = suite.CreateTest("ManualTest");
        test.Close(TestStatus.Pass);

        suite.Close();
        module.Close();

        Tracer.Instance.ForceFlushAsync().Wait();
        Console.WriteLine("Datadog Tracer Flushed!");
    }

[andrewlock]

Hi @thausercelonis, you're experiencing a consequence of one of the major changes in the migration to v2 to v3 - we no longer support manual-only tracing using Datadog.Trace; you must always enable automatic instrumentation too.

The easiest way to achieve that for your example is to use the dd-trace .NET global tool. If you install the .NET global tool, using

dotnet tool install --global dd-trace --version 3.12.0

and then run the example above, then it works as you expect:

Also note that if you use dd-trace ci run -- dotnet run, this will automatically create a test session for you, and you can remove the explicit ForceFlushAsync 🙂 e.g.

        var module = TestModule.Create("MyConsoleAppTests");
        var suite = module.GetOrCreateSuite("MyTestSuite");

        var test = suite.CreateTest("ManualTest");
        test.Close(TestStatus.Pass);

        suite.Close();
        module.Close();

//       Tracer.Instance.ForceFlushAsync().Wait(); // <- not required when using dd-trace ci run -- dotnet run
        Console.WriteLine("Datadog Tracer Flushed!");

[thausercelonis]

Hi Andrew,
thanks for your answer. It is only working, if the environment variables are set outside of the code, that means before I call dd-trace. After this change it was working.
Thanks, Thomas