Cross-Component Problem Determination Based on Logs and

Download Report

Transcript Cross-Component Problem Determination Based on Logs and

WebSphere Process Server
Cross-Component Problem Determination Based
on Logs and Common Base Events
Dr. Friedemann Schwenkreis
HPTS
September 2005
© 2005 IBM Corporation
WebSphere Process Server
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
2
HPTS
September 2005
© 2003 IBM Corporation
WebSphere Process Server
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)
3
HPTS
September 2005
© 2003 IBM Corporation
WebSphere Process Server
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.
4
HPTS
September 2005
© 2003 IBM Corporation
WebSphere Process Server
BPC
Log
Component Interaction
DB2
Log
Process
Choreographer
App
Server
Log
WebSphere
Process Server
DB2
Universal
Database
WebSphere
Application
Server
AIX
Log
AIX
5
HPTS
September 2005
© 2003 IBM Corporation
WebSphere Process Server
Example: Disk Full
 AIX: file system full error
 DB2: tablespace full error
 WebSphere Application Server:
transaction rollback exception
 Process Choreographer: audit log exception
6
HPTS
September 2005
© 2003 IBM Corporation
WebSphere Process Server
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
7
HPTS
September 2005
© 2003 IBM Corporation
WebSphere Process Server
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
8
HPTS
September 2005
© 2003 IBM Corporation
WebSphere Process Server
Advantages of Common Base Events
 Analysis tools from multiple sources/vendors
 Enable Cross-component analysis
 Extensible: Generate CBEs in your application
9
HPTS
September 2005
© 2003 IBM Corporation
WebSphere Process Server
Generic Log Adapter
Component
specific
log file entry
Transformation Rules
CBE
based
log file entry
Component
specific
adapter
plugin
10
HPTS
September 2005
© 2003 IBM Corporation
WebSphere Process Server
Example: DB2 log
11
HPTS
September 2005
© 2003 IBM Corporation
WebSphere Process Server
Example: DB2 log
12
HPTS
September 2005
© 2003 IBM Corporation
WebSphere Process Server
Log and Trace Analyzer
AIX
Visualization
Flow
DB2
Log & Trace
Analyzer
WAS
Correlation
Rules
BPC
...
13
HPTS
September 2005
© 2003 IBM Corporation
WebSphere Process Server
Questions?
www.eclipse.org/tptp/home/documents/eclipseCon2005/index.html
www.ibm.com/software/awdtools/architect/swarchitect/index.html
Friedemann Schwenkreis - [email protected]
14
HPTS
September 2005
© 2003 IBM Corporation