You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2022. It is now read-only.
Currently when we convert from a data.TraceData structure to go.opencensus.io/trace.Span structures to send to actual exports in exporterwrapper.go, none of the properties from Node are used. See the Node proto for the agent.
At least for the Stackdriver exporter, we should follow the practice of the other Stackdriver exporters and write the g.co/agent attribute based on the Node.LibraryInfo that has the language and version info for the library that wrote the spans to the agent. That would allow users to understand
what library produced the spans in a particular trace in case it needs to be upgraded.
The text was updated successfully, but these errors were encountered:
draffensperger
changed the title
Set span attribute for library/version used to write the span
Set g.co/agent span attribute for Stackdriver exporter based library/version of node
Apr 16, 2019
I have some draft code for this but need to brush it off and get it out. I'll plan to work on it over the next week or so. I am aiming to get this into both the OpenCensus and OpenTelemetry services.
Currently when we convert from a
data.TraceData
structure togo.opencensus.io/trace.Span
structures to send to actual exports in exporterwrapper.go, none of the properties fromNode
are used. See the Node proto for the agent.At least for the Stackdriver exporter, we should follow the practice of the other Stackdriver exporters and write the
g.co/agent
attribute based on theNode.LibraryInfo
that has the language and version info for the library that wrote the spans to the agent. That would allow users to understandwhat library produced the spans in a particular trace in case it needs to be upgraded.
The text was updated successfully, but these errors were encountered: