Skip to content
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

Open
JDUNNIN opened this issue Feb 5, 2025 · 5 comments · May be fixed by #4409
Open

Add more description for OTEL_BSP_SCHEDULE_DELAY #4402

JDUNNIN opened this issue Feb 5, 2025 · 5 comments · May be fixed by #4409
Labels
triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor

Comments

@JDUNNIN
Copy link

JDUNNIN commented Feb 5, 2025

URL

https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/#batch-span-processor

Description

This property is described as:

OTEL_BSP_SCHEDULE_DELAY	
Delay interval (in milliseconds) between two consecutive exports	
5000

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.

@svrnm svrnm transferred this issue from open-telemetry/opentelemetry.io Feb 6, 2025
@svrnm svrnm changed the title [Page feedback]: Add more description for OTEL_BSP_SCHEDULE_DELAY Add more description for OTEL_BSP_SCHEDULE_DELAY Feb 6, 2025
@svrnm
Copy link
Member

svrnm commented Feb 6, 2025

@JDUNNIN I moved this issue to the spec repo, since the page you were providing a feedback for, lives in this repo here.

@JDUNNIN
Copy link
Author

JDUNNIN commented Feb 6, 2025

Thanks @svrnm I had just clicked on the feedback link on page which took me here in new issue draft.

@svrnm
Copy link
Member

svrnm commented Feb 6, 2025

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!

@danielgblanco danielgblanco added the triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor label Feb 10, 2025
@danielgblanco
Copy link
Contributor

@JDUNNIN would you be able to work on a PR for this?

@JDUNNIN
Copy link
Author

JDUNNIN commented Feb 10, 2025

@danielgblanco Yes I'll find where it is and submit a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage:accepted:ready Ready to be implemented. Small enough or uncontroversial enough to be implemented without sponsor
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

3 participants