Hystrix is a latency and fault tolerance library designed to isolate points of access to remote systems, services and 3rd party libraries, stop cascading failure and enable resilience in complex distributed systems where failure is inevitable.
Currently, I don't think there is a way for HystrixFallback to know what the underlying exception was. It helps identify the real problem and help generate appropriate response through the Fallback.
Feign has a Fallback which supports visibility of underlying exception.
Currently, we are disabling the Fallback in testing to identify then actual errors. But, in PROD it can't be the case.
Currently, I don't think there is a way for HystrixFallback to know what the underlying exception was. It helps identify the real problem and help generate appropriate response through the Fallback.
Feign has a Fallback which supports visibility of underlying exception.
Currently, we are disabling the Fallback in testing to identify then actual errors. But, in PROD it can't be the case.
Let me know your thoughts