Skip to content

[bug] EntityFrameworkCore spans are not populating server.address following the otel conventions #2438

Open
@overbit

Description

Component

OpenTelemetry.Instrumentation.EntityFrameworkCore

Package Version

Package Name Version
OpenTelemetry.Instrumentation.EntityFrameworkCore 1.10.0-beta.1

Runtime Version

net8.0,net9.0, any

Description

As reported in the OTEL docs, server.address should be populated with the server domain name if available without reverse DNS lookup; otherwise, IP address or Unix domain socket name. i.e. example.com10.1.2.80/tmp/my.sock.
Meanwhile, the latest version of OpenTelemetry.Instrumentation.EntityFrameworkCore populate the field prefixing it with the connection protocol tcp.

https://opentelemetry.io/docs/specs/semconv/attributes-registry/server/#server-attributes

Steps to Reproduce

Configure the instrumentation and record some traces

Expected Result

server.address to be populated as my.domain.example
server.port to be populated as 5432

Actual Result

server.address populated as tcp:my.domain.example:5432
server.port not populated

Additional Context

No response

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingcomp:instrumentation.entityframeworkcoreThings related to OpenTelemetry.Instrumentation.EntityFrameworkCore

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions