-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
O11Y-1784: Tracing attributes should follow naming convention guidelines #54
O11Y-1784: Tracing attributes should follow naming convention guidelines #54
Conversation
Merge Requirements Met ✅Request Rosie to automerge this pull request by including @Workiva/release-management-p in a comment. General InformationTicket(s): Code Review(s): #54 Reviewers: changliu-wk, michaelyeager-wf, keruitan-wk, blakeroberts-wk Additional InformationWatchlist Notifications: None
Note: This is a shortened report. Click here to view Rosie's full evaluation. |
e0b38d2
to
a7cbf9a
Compare
Security InsightsNo security relevant content was detected by automated scans. Action Items
Questions or Comments? Reach out on Slack: #support-infosec. |
Public API ChangesRecommendation: @@ line 5: package:opentelemetry/src/api/common/semantic_attributes.dart @@
+ class SemanticAttributes
// Adding a class is a minor change.
@@ line 5: package:opentelemetry/src/api/common/resource_attributes.dart @@
+ class ResourceAttributes
// Adding a class is a minor change.
Showing results for 35d3b8d
Last edited UTC May 25 at 19:50:57 |
a7cbf9a
to
efb22af
Compare
@michaelyeager-wf This pull request has merge conflicts, please resolve. |
Confirmed that messaging calls using this version result in spans with correct attribute titles attached: https://onenr.io/01wZKzPpbR6 QA +1 |
@Workiva/release-management-p |
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.
+1 from RM
Notes
This PR makes updates to ensure that span attributes emitted by opentelemetry-dart conform to OpenTelemetry naming conventions.
Specifically:
error
has been removed. This was an attribute specific to New Relic spans which is not needed. The same effect can be gained by setting the span status to "errored".exception
has been changed toexception.type
andexception.message
.stacktrace
has been changed toexception.stacktrace
.AttributeKey
has been added to contain commonly used constant keys from the OpenTelemetry specification. At this time, these have been limited to:messaging
namespace.service
namespace.http
namespace.recordException
no longer marks a span as "errored". This is to allow consumers to record exceptions which do not represent an "error" condition for the measured operation. The Java implementation works in a similar way.Reviewers
@Workiva/observability