Bug 138410

Description Malcom Zung 2006-04-25 11:51:03 EDT

Today, the TPTP Log Viewing, Analysis and Correlation (Logging Infrastructure) capabilities are available as a single complete entity by way of the Eclipse TPTP Log and Trace Analyzer.  Downstream components, products and consumers need a set of reusable and pluggable Logging Infrastructure components that are much more granular than what we have today, and with a smaller footprint.  Consumers are saying that they want to pick and choose the Logging Infrastructure functionality they want to ship.  Some consumers want to embed a lightweight log viewer into their own application.  Others want to include analysis and correlation.  Still others want all the Logging Infrastructure functionality, but would like to provide their own GUI on top of it.  Another consumer wants to allow multiple users to view the same imported log data via web browsers.  There is also a clear need for the pluggable Logging Infrastructure to run in a diverse set of runtime environments (e.g., standalone Java app, Eclipse RCP, Eclipse IDE, servlet and web service containers, JSR 168 portlet container).

In order for this to happen, a set of APIs should be defined which provides the Logging Infrastructure functionality as services.  These APIs should be grouped, and the groups should be independent of each other.  A suggested grouping of APIs is provided in the following point features.

Import/Export https://bugs.eclipse.org/bugs/show_bug.cgi?id=137364
Analysis/Correlation https://bugs.eclipse.org/bugs/show_bug.cgi?id=137365
Browsing/Filtering/Sorting https://bugs.eclipse.org/bugs/show_bug.cgi?id=137367
User Sessions https://bugs.eclipse.org/bugs/show_bug.cgi?id=137507
Monitoring https://bugs.eclipse.org/bugs/show_bug.cgi?id=137603
Symptoms https://bugs.eclipse.org/bugs/show_bug.cgi?id=137607

The above groupings are a suggestion only, and the functionality can be rolled out in stages.  Of the groups, Import/Export of logs and Analysis/Correlation are a first priority.  

Data models that should be supported by these APIs should include Common Base Event and WEF formats.  The support for data formats should be extensisble so that additional formats may also be supported, such as extensions to WEF and company specific formats.

As these groups of APIs are defined, it should also be taken into consideration that these APIs should be mappable to WSDL, and the resulting Logging Infrastructure component(s) should be exposable as web services, running in a container such as Apache Tomcat/Axis.  This is in support of providing these APIs as services in a Service Oriented Architecture application.

Please mark this feature as P1 priority.