1 / 14

Outline

Cross-Component Problem Determination Based on Logs and Common Base Events Dr. Friedemann Schwenkreis. Outline. What is problem determination? The interaction of multiple components. Log files and correlating them Common Base Events: A canonical means to transport information

inga
Télécharger la présentation

Outline

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Cross-Component Problem Determination Based on Logs and Common Base EventsDr. Friedemann Schwenkreis HPTS

  2. Outline • What is problem determination? • The interaction of multiple components. • Log files and correlating them • Common Base Events: A canonical means to transport information • The eclipse TPTP project • Questions HPTS

  3. What is a Problem? • Invocation is rejected (non-availability problem) • Service is incorrectly performed (failure problem) • Service is correctly performed with some exceptions or additional information (potential problem) • Service is correctly performed • Quality of service requirements (e.g. timing problem) HPTS

  4. Problem Determination • Problem Detection • Simple in case of failures or non-availability • Difficult in case of potential problem cases • Hard when applications do not detect the problem • Localizing the cause • Relatively easy in a single component because all problem information is in a single log. • Difficult if the problem is caused by of other components because log information needs to be correlated first. HPTS

  5. BPC Log Component Interaction DB2Log Process Choreographer WebSphereProcess Server DB2 Universal Database AppServer Log WebSphereApplication Server AIXLog AIX HPTS

  6. Example: Disk Full • AIX: file system full error • DB2: tablespace full error • WebSphere Application Server: transaction rollback exception • Process Choreographer: audit log exception HPTS

  7. Correlating Log File Information • Problem: • Propriatory log formats • Non-uniform/component specific log content • Idea: • Introduce common format (skeleton / basis) • Agree on common content • Agree on common usage of values HPTS

  8. Common Base Events (CBEs) • Eclipse Hyades project (now: Test and Performance Tools Platform) • Fixed content: • Name, time, identification, severity • Source component identification • Situation • Variable content: • Extended context elements • Extended data elements • Extended properties HPTS

  9. Advantages of Common Base Events • Analysis tools from multiple sources/vendors • Enable Cross-component analysis • Extensible: Generate CBEs in your application HPTS

  10. Generic Log Adapter CBEbasedlog file entry Componentspecificlog file entry Transformation Rules Component specificadapterplugin HPTS

  11. Example: DB2 log HPTS

  12. Example: DB2 log HPTS

  13. Log and Trace Analyzer AIX Log & TraceAnalyzer Visualization Flow DB2 WAS Correlation Rules BPC ... HPTS

  14. Questions? www.eclipse.org/tptp/home/documents/eclipseCon2005/index.htmlwww.ibm.com/software/awdtools/architect/swarchitect/index.html Friedemann Schwenkreis - fschwenk@de.ibm.com HPTS

More Related