-
Notifications
You must be signed in to change notification settings - Fork 95
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
Expose Feign logging to enable better debugging of serialization issues #957
Comments
One thing that has been floated in the past is the idea of printing out the equivalent curl command? That way you could run the curl command from the box and capture the exact output. This also avoids us having to re-serialize things, or deal with potentially binary responses? |
That seems like a clever approach, and it would satisfy the need here so long as the curl command is usable out of the logs without a bunch of fiddling. |
This issue has been automatically marked as stale because it has not been touched in the last 60 days. Please comment if you'd like to keep it open, otherwise it'll be closed in 7 days time. |
When trying to track down de/serialization issues, it's really helpful to see the raw json that is sent back. Feign supports logging this, but conjure doesn't expose a knob to enable it.
conjure-java-runtime/conjure-java-jaxrs-client/src/main/java/com/palantir/conjure/java/client/jaxrs/AbstractFeignJaxRsClientBuilder.java
Line 102 in b401608
The text was updated successfully, but these errors were encountered: