Manual debugging would be enabling of additional debug logging locally from the controllers. Increasing log level and such to capture more information - AirWave doesn't capture the log activity, but can be used to run some of the basic cmds from controller monitoring page -> run cmd drop down options. You might also try to do a packet dump during the timeframe when users report the disconnect the most - again this is local on the controllers to perform.
AirWave can provide the trending data, and possibly alert on specific clients that are reporting the issue more frequently. But it won't have the deep dive info needed to point out the exact cause, that's data that'd be needed from the controller logs. You would be able to see the change in noise and SNR in the radio details - are you seeing a lot of channel changes / transmit power adjustments at the same time?
It's much easier to do a shared screen session than trying to talk through in a forum as there's several troubleshooting steps to go through - I suggest getting a TAC case to get such a session going.
Example path for the Aruba side:
1) On Aruba controllers, enable all debug log topics
2) Try to find out which clients see the behavior the most and time frame of the occurence.
3) See if you can connect a static client during the time frame to reproduce the disconnect. If you can reliably reproduce the drop, then it makes troubleshooting much easier.
4) Perform a packet dump from the controllers that captures when a client sees a drop
5) Provide the logging and packet dump to support to analyze
I don't currently have Cisco gear to compare the Cisco experience, but I imagine the debug steps would still be very similar.