[cdt-dev] How to monitor developer use?

[Tom Ball <tball@xxxxxxxxxx>]

At Google, we monitor use of many of our internally-deployed IDE modules, so as to better understand what how our customers are using Eclipse and figure out ways where we can improve that experience.  We'd like to extend that to include monitoring aspects of the Eclipse and CDT cores, if that can be done without forking the common base (we contribute all our changes to Eclipse code back to the community).  I'm hoping there already exists ways to handle two common cases:

. Error logging:  is there a way for an external module to hook into the error log, so errors can be forwarded?  This may be a PDE FAQ, but I haven't found any references so far.

. Action logging:  is there a general way to listen to action use?  I'm specifically interested in tracking how quickly new C++ refactorings are adopted, as poor adoption may indicate the need for better documentation and training support.  This facility is also useful for detecting inefficient UI patterns; for example, if a key-binding is never used, perhaps it needs a more mnemonic binding.

Any suggestions would be appreciated.

Tom