-
Notifications
You must be signed in to change notification settings - Fork 182
VSphere : option to enable soap client debugging #2442
Conversation
Signed-off-by: Dani Louca <dlouca@splunk.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making this change.
Would it be possible to add a test, or at least include some kind of example output when debugging is turned on? I'm pretty unfamiliar with the module being used, so I can't really tell if it's working or what the debugging output would look like. |
Thanks for looking Curtis!
Full log file https://drive.google.com/file/d/1HVvu701xV3sDN5PhEsUhmOud4srunZ_R/view?usp=sharing |
That's a fair point regarding testing. Thanks for including some example output, it helps! |
The VSphere monitor is hard to debug as the log messages don’t provide markers to where the code has failed, it only returns the low level error from the SDK.
For example, from this error, it’s almost impossible to know which API call caused it.
This bug is to allow the user to turn debugging on the SOAP client so we can see the SOAP requests/responses
Signed-off-by: Dani Louca dlouca@splunk.com