We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using the otlptracehttp exporter to export trace to a custom endpoint, I got error messages despite export succeeded:
otlptracehttp
2023/02/10 10:34:31 traces export: failed to send to [my own trace agent]: 202 Accepted
/cc @dineshg13
No error logs upon 202 Accepted responses for otlptracehttp exporter.
202 Accepted
The text was updated successfully, but these errors were encountered:
Please include a full run-able example of the error. Including the response your mock server is returning.
Sorry, something went wrong.
Hi @MrAlias I have a unit test to reproduce it and a fix in #3707. Please assign this issue to me.
We're also encountering this issue when sending traces to new-relic
This is currently blocked by the spec: open-telemetry/opentelemetry-specification#3203
songy23
Successfully merging a pull request may close this issue.
Description
When using the
otlptracehttp
exporter to export trace to a custom endpoint, I got error messages despite export succeeded:/cc @dineshg13
Environment
Steps To Reproduce
otlptracehttp
exporter against the mock backendExpected behavior
No error logs upon
202 Accepted
responses forotlptracehttp
exporter.The text was updated successfully, but these errors were encountered: