-
Notifications
You must be signed in to change notification settings - Fork 900
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
Add more description for OTEL_BSP_SCHEDULE_DELAY #4402
Comments
@JDUNNIN I moved this issue to the spec repo, since the page you were providing a feedback for, lives in this repo here. |
Thanks @svrnm I had just clicked on the feedback link on page which took me here in new issue draft. |
No worries, that's exactly why we put that link there:-) We just re-route issues if they need to go some other places. Thanks! |
@JDUNNIN would you be able to work on a PR for this? |
@danielgblanco Yes I'll find where it is and submit a PR. |
URL
https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/#batch-span-processor
Description
This property is described as:
I think it would be good to be explicitly clear that it will only be used in cases where the number of spans produced in OTEL_BSP_SCHEDULE_DELAY value time, e.g. 5s, is less than the OTEL_BSP_MAX_EXPORT_BATCH_SIZE.
For example, with the defaults of:
OTEL_BSP_MAX_EXPORT_BATCH_SIZE=512
OTEL_BSP_SCHEDULE_DELAY=5000
If in 5s only 123 spans are produced, then the OTEL_BSP_SCHEDULE_DELAY has been hit and an export of those 123 spans takes place. The converse being that in any time less than 5s, if more than 512 spans are produced, than an export will happen immediately for those 512.
Thanks.
The text was updated successfully, but these errors were encountered: