-
Notifications
You must be signed in to change notification settings - Fork 7
Transcribe attributes from span links to events #96
Transcribe attributes from span links to events #96
Conversation
Note that this patch is stacked on top of #95, but GitHub won't allow me to represent that properly here. |
0ae0c34
to
db66e5d
Compare
Yes, it looks cleaner now. Please take another look. |
@seh Apologies for the hold up with this PR. If you would please rebase again I will make sure this gets reviewed promptly. 🙏 |
Links attached to OpenTelemetry spans carry attributes like spans and events. Since we publish links as Honeycomb events, and events all carry fields, transcribe attributes on links as fields on the corresponding Honeycomb events. Include OpenTelemetry resource attributes as the underlay, and shadow those resource attributes if necessary with the link-level attributes.
db66e5d
to
9a2e994
Compare
This was a blast from the past. Please see the latest commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question for clarification, otherwise looks good! Thanks!
|
||
// Treat resource-defined attributes as underlays, with any same-keyed span attributes taking | ||
// precedence. Apply them first. | ||
applyResourceAttributes(ev) | ||
if len(e.serviceName) != 0 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why remove adding service_name
to the event here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See lines 508-511 above. It still happens as part of the call to applyResourceAttributes
at line 521.
Links attached to OpenTelemetry spans carry attributes like spans and events. Since we publish links as Honeycomb events, and events all carry fields, transcribe attributes on links as fields on the corresponding Honeycomb events.
Include OpenTelemetry resource attributes as the underlay, and shadow those resource attributes if necessary with the link-level attributes, as we did for spans and span events in #71.