Mixing OpenTracing and automatic instrumentation

I’m using 1.7 of the .NET stuff for .NET Core. I followed the example on how to add OpenTracing to my DI and sprinkled it thru my code. (https://docs.datadoghq.com/tracing/advanced/opentracing/?tab=net)

public static IServiceCollection AddTracer(this IServiceCollection services)
{
  ITracer tracer = OpenTracingTracerFactory.CreateTracer();
  GlobalTracer.Register(tracer);
  services.TryAddSingleton(tracer);
  return services;
 }

using (IScope scope = _tracer.BuildSpan(someSpan).StartActive())
{
 // logic
}

However, I’m not seeing the the custom traces/spans on the flame charts. I am seeing the automatically instrumented spans.

Is there a special sauce I’m missing? Does this require a certain version of the agent to be run?

(edit: formatting)

[zacharycmontoya]

Hi @daniel-white, we’ve just released version 1.8.0 of the tracer which adds a new API OpenTracingTracerFactory.WrapTracer (thank you @alexeyzimarev for the contribution!). Using this for your use-case should look like the following:

public static IServiceCollection AddTracer(this IServiceCollection services)
{
  ITracer tracer = OpenTracingTracerFactory.WrapTracer(Datadog.Trace.Tracer.Instance);
  GlobalTracer.Register(tracer);
  services.TryAddSingleton(tracer);
  return services;
}

Please let us know if you run into any other issues and feedback, as we’re looking to better support manual instrumentation and OpenTracing scenarios.

[alexeyzimarev]

@colin-higgins the issue is that the Datadog tracer is very limited. I cannot find any way to access the scope context and extract/inject it for distributed tracing. OpenTracing has it all. Without distributed tracing, the whole tracing idea is almost pointless.