Description
What's the issue?
We allow users to run collect-logs whilst other operations are running e.g. collecting the logs for a hanging backup.
We currently don't capture a goroutine stack trace in these cases, in theory these would be extremely when debugging issues such as a hanging backup.
What's the fix?
We should look to see if we can leverage our SIGQUIT behavior to force all running instances of cbbackupmgr to dump stack traces.