OpenTelemetry Go implementation traces not showing in `Distributed Tracing` tab


I am trying to implement OpenTelemetry using Since our account is setup in the EU datacenter, I had to override theSpansURLOverride to use the .eu subdomain. I don’t know if this has an impact. Without this the API returned 403 Forbidden.

I have it set up and everything. When I try to add a trace I get the following logs:

   "data": [
      "common": {},
      "spans": [
          "id": "73bda0f20665838d",
          "": "48f44bd474f5833d487960a0ea01edcf",
          "timestamp": 1608554828768,
          "attributes": {
            "name": "login",
            "": 98.3224,
            "": "LOCAL auth",
            "span.kind": "internal",
            "instrumentation.provider": "opentelemetry",
            "": "newrelic-opentelemetry-exporter"
  "event": "uncompressed request body",
  "url": ""

And the API responds with:

  "body": {
    "requestId": "ba1694f9-0001-b000-0000-01768556eed4"
  "event": "data post response",
  "status": 202

However, I am still not able to see the traces in the Distributed Tracing tab of the service.
If I use the package directly using the newrelic.WrapHandleFunc function, I can see the transaction in the Distributed Tracing tab.

This is the current attempt at implementing:

exporter, err := newrelic.NewExporter(
	if err != nil {
		fmt.Printf("failed to instantiate New Relic OpenTelemetry exporter: %v\n", err)

	ctx := context.Background()
	defer exporter.Shutdown(ctx)

	// Create a tracer provider
	bsp := sdktrace.NewBatchSpanProcessor(exporter)
	tp := sdktrace.NewTracerProvider(sdktrace.WithSpanProcessor(bsp))
	defer func() { _ = tp.Shutdown(ctx) }()

	// Set global options

And in our controller we do this:

	var span trace.Span
	tracer := otel.Tracer("SuperTestLogin")
	ctx, span := tracer.Start(req.Context(), "login")
	defer span.End()

	span.AddEvent("Nice operation!", trace.WithAttributes(label.Int("bogons", 100)))


Best Regards,

I found out that the integration had created a new service instead of using the existing one.
So this seems to work as it should.

Is it possible to merge this new Integration-reported services into a Service?



@jarl Thank you for sharing that you found the issue with your integration. I notice you have an additional question and wondering if you are still looking for information on how to merge into a service?

Hi @JoiConverse,
Yes! It’s kind of annoying having multiple services for the same thing. It’s quite crowded in a micro-service environment having every service multiple times for every environment :slight_smile:


Hey @jarl,

Entities that belong to the Service group are created by our own language agents. The Integration-reported services are entities created, in this case, through Trace API. At this time, there isn’t a way to merge these services together. They should both appear on the Services list in New Relic One.

I hope this helps. If you have any questions at all, please let us know!