Skip to content

Should client.port be changed to opt-in on HTTP server spans? #470

@trask

Description

@trask

It doesn't seem to have much value for a recommended attribute.

The only argument I can think of is for correlation with HTTP client spans, but client.port is already opt-in on HTTP client spans.

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