Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[exporter/newrelic] instrumentation.provider attribute is missing #2621

Closed
F21 opened this issue Mar 9, 2021 · 2 comments
Closed

[exporter/newrelic] instrumentation.provider attribute is missing #2621

F21 opened this issue Mar 9, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@F21
Copy link

F21 commented Mar 9, 2021

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.md

This appears to be missing in the exporter and spans sent to new relic are missing this attribute.

Steps to reproduce

  1. Instrument an app (I used the Go SDK)
  2. Point the app to use an opentelemetry collector with the new relic exporter.
  3. Filter entities in the explorer with 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?

receivers:
  otlp:
    protocols:
      grpc:
processors:
  batch:
exporters:
  newrelic:
    apikey: NEW_RELIC_KEY_GOES_HERE
    timeout: 30s
service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [newrelic]
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [newrelic]

Environment
OS: Minikube in docker mode

@F21 F21 added the bug Something isn't working label Mar 9, 2021
@gunturaf
Copy link
Contributor

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.

Firstly I came across this code in the newrelic/opentelemetry-exporter-go repo. https://github.com/newrelic/opentelemetry-exporter-go/blob/e563425c51c9e256b329c37e72192baac0396aca/newrelic/internal/transform/span.go#L63

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),
)

I'll volunteer for PR if this issue is confirmed.

cc-ing NR code owners @alanwest @a-feld @jack-berg @nrcventura

@F21
Copy link
Author

F21 commented Apr 2, 2021

Fixed in #2900

@F21 F21 closed this as completed Apr 2, 2021
ljmsc referenced this issue in ljmsc/opentelemetry-collector-contrib Feb 21, 2022
Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants