-
Notifications
You must be signed in to change notification settings - Fork 254
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
OTLP metrics export partial success - structure, semantic conventions and beyond #404
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #390 we introduced the concept of partial success in OTLP export responses. The initial version only contained fields to indicate the # of accepted datapoints + a string error message. During the PR review it was brought up that only these fields might not be enough and that we may need more structure to be able to achieve more things with it.
This issue is to continue the discussion, focusing on what we want to achieve and agree on how we want to do it.
A couple of things that came up was:
Derive telemetry for consumed/dropped metrics for OTLP exporters
Exporters would record metrics using the
partial_success
response. Things likeotlp.metrics.consumed
,otlp.metrics.dropped
can be derived from the # of accepted datapoints. With the current structure we defined in #390 this is already possible, but we need to define semantic conventions for these metrics so OTLP exporters are consistent in how they report it (if desired).Action items:
Possibility to retry
With only the # of accepted datapoints + a string error message we currently have, it's not possible to achieve any level of retry. It might be possible to perform a retry in some cases but to do that, we need more structure on the
partial_success
result.From the PR, an example of such response would be:
Another important topic was that any extra details should be optional to not overload receivers/senders that are under pressure.
Action items:
The text was updated successfully, but these errors were encountered: