Capture DCP Stats on termination of unsuccessful rebalance

The DCP stats from cbstats dcp often prove very useful to debugging the state of a problematic stream. These stats are captured at the time of a cbcollect and periodically (every 10 mins I believe) by ns_server. The problem is that this leaves a certain amount of guesswork as to what was going on at the time of a rebalance failure. Would it be sensible and possible to invoke this stats collection at the time of a failed rebalance, prior to the DCP streams involved in the rebalance being torn down?