|
SysGMon is a scalable, dynamic and flexible monitoring tool based on the
non-intrusive and event filtering architecture for monitoring,
diagnosing, and correcting large scale distributed J2EE systems.
This tool based upon the above mentioned architecture, detects predefined
events and performs either corrective or steering action.
When appropriate, information is also disseminated to the management
applications or administrators.
Proposed solution and Design Architecture
The outlined solutions offers improvements over related works by
introducing non-intrusive monitoring technique
based on the hierarchical events filtering. The results are:
Minimal intervention:
SysGMon tool can be installed on the client
computer and it communicates to the system directly using the
predefined Simple Object Access Protocol (SOAP) or Remote Method
Invocation (RMI) communication protocols, meaning there is no
monitoring agent need to be installed on the production system,
thus there is very minimal to non intervention but in the same time
it provides dynamic and flexible way of control. For example,
consumers can change the instrumentation instructions at run-time.
Minimal to non intrusiveness:
SysGMon employs the technique called
non-intrusive architecture to minimize the impact of the monitoring
system on the monitored application, meaning it does not overwhelm
the system resources such as the computation or network resources.
Currently available features:
- This tool has been written in such a way that it can either be run
as a client or Websphere custom service.
- No need to change the code in order to add/remove the WebSphere
Events Notifications type. This can be done through the property file.
- If needed, thread dump can be set for any events through the property
file. For example, it is very useful to automatically detect the Hung
Thread problem and do a thread dumps whenever it happens.
- Can be customized easily to notify Administrator whenever the problem
occurs. Currently, email notification method has been implemented.
- Standalone admin client can either connect through the SOAP or RMI
to WebSphere Server. Connection method can be set through the property
file.
Features under development:
- Implement interface for other J2EE application servers like Bea Weblogic,
JBOSS, Sun Java systems.
- Provide events persistent features so that events can either be
persisted in the database or in XML file for problem tracking and
configuration management purpose.
- Provide Graphical User Interface to configure the SysGMon
- Provide interface for automated corrective measures.
|
