[jira] [Reopened] (DTACLOUD-44) Deltacloud daemon needs debug level verbosity options to allow effective diagnosis of communications problems

["Ronelle Landy (Reopened) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DTACLOUD-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ronelle Landy reopened DTACLOUD-44:
-----------------------------------


Reopening issue as per response from Justin Clift:

>From looking at that example server trace, it's just summary info.  Not (even close) to "debug" level.

Debug level logging would show everything occurring.
i.e: http headers for each request, full response logging for each request, and so on

                
> Deltacloud daemon needs debug level verbosity options to allow effective diagnosis of communications problems
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DTACLOUD-44
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-44
>             Project: DeltaCloud
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Justin Clift
>            Assignee: David Lutterkort
>
> At present, when communication problems seem to be occurring between Deltacloud and any given Cloud provider, debugging them is very difficult/opaque.
> As a step towards making this practical to work with in the Real World, having deltacloudd log (debug level) information to a log file would be beneficial.
> By "debug level" I'm meaning logging all communications to any given cloud provider (timestamped), including sensitive info (usernames, passwords, etc), and also logging all return information (status codes, data, etc).
> This debug level verbosity would not be something left on in most circumstances, as the volume of data could be massive for some things (image transfers?), but some mechanism to assist in debugging connection/weird problems is needed. Sooner rather than later.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira