-
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-1528 : update sdk to use api where possible #36
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): #36 Reviewers: changliu-wk, blakeroberts-wk Additional InformationWatchlist Notifications: None
Note: This is a shortened report. Click here to view Rosie's full evaluation. |
Security InsightsNo security relevant content was detected by automated scans. Action Items
Questions or Comments? Reach out on Slack: #support-infosec. |
a44ef0b
to
c9517d0
Compare
The ConsoleExporter has no requirements, and has no configuration options. | ||
``` | ||
|
||
```dart | ||
import 'package:opentelemetry/sdk.dart' as otel_sdk; | ||
|
||
final exporter = otel_sdk.ConsoleExporter(); |
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.
There's an extra "a" on line 44 under Span Processors: "Next, you will need a at least one span processor."
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 that was like a cool guy pause for dramatic effect, "Next, you will need ay .. eh ... at least one span processor."
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.
Also LIne 44, "A span processor is responsible for collectoring the spans you create and feeding them to the exporter." should be "collecting"?
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.
lol yes. But I am definitely adding collectoring to my vocabulary haha
QA +1 tested using local build and wk-dev: https://onenr.io/0YBR6pXDqQO |
QA +1 |
lib/src/api/trace/span_context.dart
Outdated
import 'trace_flags.dart'; | ||
import 'trace_id.dart'; | ||
import 'trace_state.dart'; | ||
import '../../../api.dart' as api; | ||
|
||
/// Representation of the context of the context of an individual span. |
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.
Should this line be "Representation of the context of an individual span"?
lib/src/api/trace/span.dart
Outdated
|
||
// Retrieve the resource on this span. | ||
Resource get resource; | ||
api.Resource get resource; | ||
|
||
// Retrieve the resource on this span. |
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.
This comment should be "Retrieve the instrumentationLibrary"?
QA +1 here are some spans https://onenr.io/0bEjOJM08R6 |
@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
https://jira.atl.workiva.net/browse/O11Y-1528
What
Any use of a class within SDK should use the API version where possible. What this means is that the type definitions of class fields, return types, and argument types should use the API version; however, instantiation of the implementation of an object must use the SDK type (as that is the type that holds the concrete implementation of the API type).
Note
I also removed the SDK class for
TraceFlags
in favor of a bitmap housed within the API package. I believe this is a more concise and accurate representation of the underlying mechanism of the W3C trace context and more closely aligns with the JavaScript implementation.@Workiva/product-new-relic