-
Notifications
You must be signed in to change notification settings - Fork 851
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
exporter-collector-http: log error when it fails to export #1459
Comments
@vmarchaud sure |
@vmarchaud I think this will be irrelevant once the global error handler is implemented -> #1415 |
Well on the error handling side yes, one thing we could add on the error still is the response body. |
I needed that for my deployment so i've developped it, hope you didn't started that in the mean time |
@vmarchaud does #1607 fix this issue? If so, please link the PR. |
@dyladan Done, i though it was autoamtic if i tagged the issue in the PR title :/ |
Co-authored-by: Daniel Dyla <[email protected]>
Currently the collector-exporter in HTTP just log that the export failed with only the status code. We should get the error and log it in the console for end users to find what's wrong.
For example i was debugging an 400 and to debug i had to publish another package with more logs to see that the error was:
cc @obecny do you want to tackle it ?
The text was updated successfully, but these errors were encountered: