You can use APIs, MBeans, logs, and utilities to monitor
the performance of your application environment.
Statistics overview
Statistics in WebSphere® eXtreme Scale are
built on an internal statistics tree. The StatsAccessor
API, Performance Monitoring Infrastructure (PMI) modules, and MBean
API are built from the internal tree.
Monitoring with the statistics API
The Statistics API is the direct interface to the internal statistics tree. Statistics are disabled by default, but can be enabled by setting a StatsSpec interface. A StatsSpec interface defines how WebSphere eXtreme Scale should monitor statistics.
Monitoring performance with WebSphere Application Server PMI WebSphere eXtreme Scale supports
Performance Monitoring Infrastructure (PMI) when running in a WebSphere Application
Server or WebSphere Extended Deployment application server. PMI collects
performance data on runtime applications and provides interfaces that
support external applications to monitor performance data. You can
use the administrative console or the wsadmin tool to access monitoring
data.
Using Managed Beans (MBeans) to administer your environment
You can use several different types of Java™ Management Extensions (JMX) MBeans to administer and monitor deployments. Each MBean refers to a specific entity, such as a map, eXtreme Scale, server, replication group, or replication group member.
Using the xsAdmin sample utility
With the xsAdmin sample utility, you can format and display textual information about your WebSphere eXtreme Scale topology. The sample utility provides a method for parsing and discovering current deployment data, and can be used as a foundation for writing custom utilities.
Vendor tools WebSphere eXtreme Scale can be monitored using several popular enterprise monitoring solutions. Plug-in agents are included for IBM® Tivoli® Monitoring and Hyperic HQ, which monitor WebSphere eXtreme Scale using publicly accessible management beans. CA Wily Introscope uses Java method instrumentation to capture statistics.
Logs and trace
You can use logs and trace to monitor and troubleshoot
your environment. Logs are in different locations depending on your
configuration. You might need to provide trace for a server when you
work with IBM support.