Did you see the article here? http://community.arubanetworks.com/t5/Community-Tribal-Knowledge-Base/How-to-troubleshoot-user-connectivity-issues-on-Instant-AP/ta-p/82142
Please keep in mind, you will only see something if a client timed out of the table, roamed, or the AP disassociated the client. If a client gets disconnected because of interference, or cannot get enough airtime to transmit or is out of range, it will not show up there. That information would have to be obtained on the client, somehow. The priority is to design a network that has enough capcity, coverage and is designed to be resilient to interference and congestion. When you do that, if there are issues, they are minimized. It is not feasible to debug each client realtime, so you have to create an environment for most clients to be successful, then troubleshoot the outliers. If all clients are having a problem, how the network is designed and provisioned needs to be looked at. If it is a single client, that client needs to be troubleshot.