Conversation
This will allow us to define asynchronous span exporters, if the span processor will be async as well.
aabmass
left a comment
There was a problem hiding this comment.
I would love to see this issue tackled. I think the tough part is, how do you update the span processors to know if they have a sync or async exporter? I think it would also be useful to have an AsyncBatchSpanProcessor which replaces the background running thread with an async task
I agree. The next step would be to define an async span processor. You're welcome to join the effort. It'll be quicker to implement this way. |
|
This PR has been automatically marked as stale because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 days of this comment. |
Description
This PR will contain an API for asynchronously exporting spans, logs and metrics.
Fixes #62
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
It hasn't yet but it will have unit tests and we will test it manually.
Does This PR Require a Contrib Repo Change?
Answer the following question based on these examples of changes that would require a Contrib Repo Change:
The OTel specification has changed which prompted this PR to update the method interfaces of
opentelemetry-api/oropentelemetry-sdk/The method interfaces of
test/utilhave changedScripts in
scripts/that were copied over to the Contrib repo have changedConfiguration files that were copied over to the Contrib repo have changed (when consistency between repositories is applicable) such as in
pyproject.tomlisort.cfg.flake8When a new
.github/CODEOWNERis addedMajor changes to project information, such as in:
README.mdCONTRIBUTING.mdYes. - Link to PR:
No.
Checklist: