-
Notifications
You must be signed in to change notification settings - Fork 792
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
Handle partial success responses from OTLP export services #3183
Comments
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
pichlermarc
added
the
up-for-grabs
Good for taking. Extra help will be provided by maintainers
label
Dec 5, 2022
3 tasks
pichlermarc
removed
the
up-for-grabs
Good for taking. Extra help will be provided by maintainers
label
Nov 15, 2023
7 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Statement
Following the specification change to add partial success responses, each OTel SDK is encouraged to handle the resulting error message string in an appropriate way, considering existing norms. This requires OTLP v0.19.
Proposed Solution
For each of the
Export*ServiceRequest
methods used by OTLP Trace and Metrics exporters, construct an error and call the appropriate handler with the error message string and the number of spans/points(/logs) dropped. Future OTel specifications may call for optional treatment of the number of dropped items, but presently that is just additional information to include in the handled error.The text was updated successfully, but these errors were encountered: