Improvement on CloudSDK Logging

[prateekbajaj15]

Describe the Problem

Joule currently leverages on CloudSDSK to fetch BTP Destinations via the following method call of CloudSDK:
tryGetDestination( @nonnull final String destinationName, @nonnull final DestinationOptions options )

However, whenever there is an error seen in such a call, the destination call might be failing due to various reasons like – credentials not valid, token expired, etc., the standard error that is shown in the logs suggests: "Destination Not Found"

Would it be possible to enhance the logging to segregate finer-grained error details to allow better debugging/logging

Propose a Solution

Provide fine-grained logging based on specific errors observed (instead of the standard "destination not found" errors logged at the moment).

Describe Alternatives

No response

Affected Development Phase

Development

Impact

Impaired

Timeline

No response

[newtork]

Please provide an example.

In troubleshooting phase we regularly recommend using the Apache wire-logs to print full HTTP traffic.
Since we cannot cover 100% of potential error cases, there are too many. That's why we have prepared exception- and logging messages. Please find the exception causes and suppressed exceptions, for logging please use debug level when in doubt.