fix(EntityFrameworkCore): server.address field to follow otel conventions #2439
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2438
Update the
server.address
field in EntityFrameworkCore spans to populate with the server domain name without thetcp
prefix.Changes
src/OpenTelemetry.Instrumentation.EntityFrameworkCore/Implementation/EntityFrameworkDiagnosticListener.cs
to fetch thehost
andport
properties from theconnection
object and set them to theserver.address
field, with a fallback to use thedataSource
property if thehost
property is not available.src/OpenTelemetry.Instrumentation.EntityFrameworkCore/CHANGELOG.md
to reflect the changes made to theserver.address
field.src/OpenTelemetry.Instrumentation.EntityFrameworkCore.Tests/EntityFrameworkInstrumentationTests.cs
to verify theserver.address
field is populated correctly without thetcp
prefix.Merge requirement checklist
CHANGELOG.md
files updated for non-trivial changes