Skip to content

BatchProcessing for Spans should use own thread by default #2454

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.

Sign up for GitHub

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

Jump to bottom
Closed
cijothomas opened this issue Dec 19, 2024 · 0 comments · Fixed by #2456
Closed

BatchProcessing for Spans should use own thread by default #2454

cijothomas opened this issue Dec 19, 2024 · 0 comments · Fixed by #2456
Labels
A-trace Area: issues related to tracing good first issue Good for newcomers help wanted Good for taking. Extra help will be provided by maintainers/approvers
Milestone
0.28.0

Comments

@cijothomas
Copy link
Member

Need to do a similar improvement as already done for logs and metrics.
#2436
@cijothomas cijothomas added this to the 0.28.0 milestone Dec 19, 2024
@cijothomas cijothomas added good first issue Good for newcomers help wanted Good for taking. Extra help will be provided by maintainers/approvers A-trace Area: issues related to tracing labels Dec 19, 2024
@lalitb lalitb mentioned this issue Dec 19, 2024
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-trace Area: issues related to tracing good first issue Good for newcomers help wanted Good for taking. Extra help will be provided by maintainers/approvers
Projects
None yet
Milestone
0.28.0
Development

Successfully merging a pull request may close this issue.

BatchSpanProcessor with dedicated thread. lalitb/opentelemetry-rust
1 participant
@cijothomas