Open sdaubin opened 5 months ago
Attention: Patch coverage is 35.71429%
with 27 lines
in your changes missing coverage. Please review.
Project coverage is 70.63%. Comparing base (
7a8faab
) to head (35c91f8
). Report is 37 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
While this PR has been reviewed and approved, I'm changing it to a draft to prevent merging as there are ongoing discussions about the broader OTel strategy across APM and we want to make sure that all teams are in alignment on an approach.
Overview
The java agent supports auto configuring the OTel SDK to report data to New Relic. Spans that are created with the span api are orphaned from New Relic data structures though. This returns spans backed by NR traces to generate metric and DT data.
This change hooks the
SdkTracerProvider.tracerBuilder
method and returns our tracer builder. When spans are started, we attempt to create a tracer. If successful, we return aSpan
implementation backed by the tracer, otherwise we return a no op span.There is some special logic based on the span kind:
consumer
We start an OtherTransaction for
consumer
span kind.server
We start a transaction for server spans and turn it into a web transaction.
client
For client spans, we either turn it into a database span or an external based on the span attributes.
Configuration
opentelemetry.sdk.spans.enabled
can be use to disable the span behavior.opentelemetry.instrumentation.{instrumentation-scope}.enabled
can be used to disable spans for a specific Opentelemetry libraryRelated Github Issue
Include a link to the related GitHub issue, if applicable
Testing
The agent includes a suite of tests which should be used to verify your changes don't break existing functionality. These tests will run with Github Actions when a pull request is made. More details on running the tests locally can be found here,
Checks