Bug 144034

Description Ashish Patel 2006-05-26 16:07:46 EDT

Need extensible mechanism to plug statistical data collectors into TPTP such that I can develop my own data collector and the UI to configure that data collector within the profiling launch configuration dialog.

I would like to see the replacement of the Host, Agent, and Settings tab when you configure a statistical launch configuration.  I would like to see two things:

1) ability to plugin my own statistical data collector
2) not have the UI or runtime of launch mechanism tied to the RAC or the concept of the RAC in any way (ie. today you specify the HOST that has the RAC on it.  I'd rather specify the host where the data collector is located.)  
3) The pluggability for statistical agents (or any Data Collection Mechanism) should allow one to contribute their own UI for configuration and their own Launch Delegate.  Therefore, I want to provide my own UI to configure this data collector, rather than having a table with parameters and values.  For instance I may want to contribute a TreeViewer that lists counters from a data collector for a user to pick from.

Some notes:

1)	The work in #93212 would allow us to provide our own Launch Delegates, rather than using one common delegate as in today’s statistical code.  This would allow our ITM and rstatd agents to use their own API, which is not RAC-centric, to launch itself. 

2)	Today, the statistical launch configuration is the only launch configuration that doesn’t follow the same launch configuration types as the Profile/Monitor tab.  Having this consistency across all agents (whether they are trace or statistical agents) is a major step towards consistency in TPTP.

3)	There is also the benefit of having the capability to associate stat data collectors with other configurations such as Java application.  This will give the user the ability to for example monitor system resources as a process executes.