Skip to content

Should server.address and server.port be changed from required to recommended on SERVER spans? #111

@trask

Description

@trask

Spinning this out from #109 as a separate issue.

Summarizing the discussion:

Pro: server.address and server.port are interesting, but not essential on SERVER telemetry for the tracing experience (because you can typically get similar identification of the service from service.name)
Con: being able to reconstruct url on server telemetry is useful
Pro: reconstructing url is not reliable since server.address and server.port typically come from Host header

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions