You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I came across this issue too, this causes my Traces to only visible on the "Distributed Tracing" page in the One UI APM page, while not being visible as Transactions in the APM.
My traces will correctly shown in the Transactions page when I manually add the instrumentation.provider = opentelemetry attribute to my Traces. The immediate workaround I did was like this:
serviceAttr:=resource.NewWithAttributes(
semconv.ServiceNameKey.String("something-something"),
semconv.ServiceNamespaceKey.String("group-of-something"),
attribute.String("instrumentation.provider", "opentelemetry"), // add this one
)
pusher:=otelController.New(
// other opts...otelController.WithResource(serviceAttr),
)
Describe the bug
According to the opentelemetry spec for new relic, there should be an
instrumentation.provider
attribute:https://github.com/newrelic/newrelic-exporter-specs/blob/master/opentelemetry/OpenTelemetry-Spans.mdThis appears to be missing in the exporter and spans sent to new relic are missing this attribute.
Steps to reproduce
instrumentation.provider = opentelemetry
and see that the entities do not show up.What did you expect to see?
Spans sent to new relic should have the
instrumentation.provider
attribute set.What did you see instead?
The
instrumentation.provider
attribute was not set.What version did you use?
v0.21.0
What config did you use?
Environment
OS: Minikube in docker mode
The text was updated successfully, but these errors were encountered: