-
Notifications
You must be signed in to change notification settings - Fork 36
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-3733: opentelemetry-dart: Implement Improvements to Timer in BatchSpanProcessor #137
Conversation
Loaded these changes in a small testing application and confirmed that it can be used to properly emit traces. QA +1 |
Security InsightsNo security relevant content was detected by automated scans. Action Items
Questions or Comments? Reach out on Slack: #support-infosec. |
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 behavior is in accordance with the spec.
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#batching-processor
One thing that is missing is immediate batch export once maximum batch size has been reached, but that was missing before too. It should be added separately.
⛄
@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
Which problem is this PR solving?
The implementation of Timer for periodic export of spans from BatchSpanProcessor is convoluted and not as null-safe as it should be.
This PR simplifies how BatchSpanProcessor uses Timer in emitting spans.
How Has This Been Tested?