-
Notifications
You must be signed in to change notification settings - Fork 630
[Tracing] Consistent span attribute key for CloudEvent id #4578
Copy link
Copy link
Closed
Labels
area/conformancearea/observabilitykind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.kind/good-first-issueDenotes an issue ready for a new contributor.Denotes an issue ready for a new contributor.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
Metadata
Metadata
Assignees
Labels
area/conformancearea/observabilitykind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.kind/good-first-issueDenotes an issue ready for a new contributor.Denotes an issue ready for a new contributor.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
MTBroker filter and ingress use
messaging.message_id:eventing/pkg/tracing/attributes.go
Lines 30 to 44 in 2e9f6a2
and the dispatcher uses
cloudevents.id:eventing/pkg/kncloudevents/populate_span_transformer.go
Lines 38 to 44 in 2e9f6a2
Expected Behavior
Consistently use one of them because using both is confusing.
Additional context
The open telemetry spec defines
messaging.message_idas follow:cloudevents.idmakes sense but it's not a well-known key for tracing.Which one do we want to choose?
/area observability