Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In batch_processor and simple_processor the exporter:init is moved out of the
gen_statem
init
. If it fails (returnsundefined
) then theinit
will beattempted again each time spans are to be exported.
The only issue is the warnings about failing to init the exporter
will continue to print forever if it can never initialize. We
can't simply stop trying to init if the failure is one that can
never resolve on its own because the exporter can be changed at
anytime by the user.
This is not meant to be used for retry logic and has no exp
backoff. It is only meant to deal with issues like the exporter's
deps not being started when the SDK tries to init the exporter and
it will soon successfully init because the release is in the
process of booting.