Download End-to-End e-business Transaction Management

Selecting the Timer.doGet() node and examining the inspector would show any
metrics captured for the Servlet. In this example, the Servlet tracing is minimal,
and the following figure is what would be displayed by the inspector (Figure 2-8).
If greater tracing were specified, the context metrics could provide information on
SQL statements, login information, and so on (some of the later chapters will
demonstrate this), depending on the type of node selected and the level of
tracing configured in the listening policy.
Figure 2-8 Inspector viewing metrics
Using these steps, the administrator has very quickly determined that the cause
of the poor performance is a particular servlet, and the root cause is a specific
method (Timer.doGet()) of that servlet. Narrowing the problem down this quickly
to a component of an application would previously have taken a lot of time and
effort, if it was ever discovered at all. Often, it is all just a little too hard to find the
problem, and the temptation is to buy more hardware. This administrator has just
saved his organization the expense of purchasing additional hardware because
of a poorly performing servlet method.
Other reports provided with TMTP
Some of the other reports available from within TMTP are shown in this section.
Overall Transactions Over Time
This report (Figure 2-9 on page 49) can be used to investigate the performance
of a monitored transaction over a specified period of time.
48
End-to-End e-business Transaction Management Made Easy