70 WebSphere Studio Application Monitor V3.2 Advanced Usage Guide
Load burst: A sudden additional load followed by an increase of response
time. If the increase is more than proportional to the load increase, then it may
be an application problem that is not tuned properly to handle more load.
Some special situations may occur for new or changed applications. These
changes require the operator to take on additional monitoring tasks. This
includes performance tuning for the new application, as discussed in 4.4,
“Performance tuning” on page 78. Also, additional reports may be generated to
understand the impact of the new or changed application in the production
environment.
4.3 Reports
WebSphere Studio Application Monitor offers an extensive set of reports about
collected data. These are accessible via PERFORMANCE ANALYSIS →
CREATE REPORTS. The data in these reports is from the database and offers
the best look at historical data.
Reports are useful for:
Providing summary information about application server performance in an
interval. This can also be scheduled regularly with PDF output.
Showing long-term trends for growth of resource usage to allow preventative
maintenance to occur.
Assisting in capacity predictions of potential bottlenecks to allow for
maintenance upgrades or preparation of new hardware.
Comparing information from different time intervals, such as having a
baseline for a good day to compare with a bad day.
4.3.1 Report types
This section contains descriptions of the report types that are available with
WebSphere Studio Application Monitor: application reports and server reports.
Application reports
Six reports are designed to monitor applications:
Request/Transaction Compares requests over time and drills into specific
requests and their transaction breakdown/flow. Useful for
finding past errant behavior and examining the causes
by going into detail using the drill-down feature.