Usage

This section describes the usage of Anyframe Monitoring Tool in detail.

The modules in the Anyframe Monitoring Tool are discussed.

Select Dialogue

The "Select Dialogue" has three functionalities. The first is to select the applications and instances that are connected with the Anyframe monitoring tool. When some execution is done on a sample application such as eMarketplace, an application with its instance pops up under “Select Applications.” Thus, this allows for connecting with various applications that we want to monitor. The second functionality is whether to monitor the application’s “Live Data” or monitor in “Archive Mode.” This functionality allows for a real-time monitoring of the data or selects an interval and monitor the aggregate data collected so far in the interval selected with the calendar.

Lastly, the “Show labels for graph” either makes graphs with labels on the screen or no labels showing. In the lower window, we see the monitoring screen. It is divided into the header, footer, left panel, top-right, bottom-right and the two middle sections that divide the header with the lower portions of the monitoring tool. The first location that we are at is the sample-web, tree. This top item shows the four items in the summary section which are namely the statistics for HTTP, SQL and JDBC. Other additional layers such as the application service may be added (noted in configuration.) The total time and count for each items are displayed. The corresponding graphs are shown with respect to time and counts with different colors and sizes of portions.

The two pictures show graphs with/without labels.

Absolute Panel

The HTTP panel shows the statistics information for the HTTP calls that are executed in the attached program. The HTTP calls are monitored and its data is shown as graphs for the execution time and count. The program’s function trace paths are shown in the trace window, displaying the total, execution times and count.
The statistics window shows the total time, count, average time, minimum execution time, maximum execution time, first executed and last executed times. The total time is the total time elapsed for a call. The count is the number of executions. The average time is the average time for the called executed so far. The adjusted average time is the average excluding the first execution. The minimum and maximum execution times are the fast and longest times for a call. The first and last executed times are the first and the last execution times for a series of calls.
The following scheme is followed for the blue bars
  • The bar for the root operation is completely colored and have the largest size
  • The bar size for each next level is equal to the colored part of its parent bar
  • The colored part of the bar for operation is the percent of its Total Time relatively to its parent Total Time
With these bars, the bottlenecks of an application are monitored. The following pictures show the different data collected from the Anyframe monitoring tool. The one shows the data collected from the Application level. The application contains the data for items such as HTTP, SQL, JDBC and etc. These data are shown together in one statistics window. The below picture to the right shows the JDBC information (e.g. JDBC operation’s stats.)

The first picture shows the top five SQL executions with its statistics. The detailed window shows all the SQL’s that have been called so far and there is a tooltip to display the SQL command for each line. Also, the SQL’s may be viewed by clicking on each line, and the content will be shown in the bottom of the window.
In the SQL statistics window, in the first column, the total average time is shown. For the following columns, the average time, count of calls, maximum time, minimum time, first execution time and last execution time are shown with respect to execute and prepare statements.

Hierarchical Panel

Absolute layer summary shows the time spent in each layer. Hierarchical layer summary show the time of the last layer in the dotted notation when this layer is called from the layers that precede it in the layer name (For example, if the layer is Web.Xpetstore.JDBC the time displayed is the time spent in the JDBC layer when called from the Layer Web.Xpetstore). The below pictures show the top level statistics with respect to different hierarchies and the HTTP layer.

Aside from the difference mentioned above, the hierarchical panel has the same types of functionalities. Each of the SQL, HTTP, JDBC statistics are shown according to above schemes. The graphical user interface, graphs, and Ajax functionalities are all the same. The general appearance of the monitoring windows is the same. The below pictures show the SQL statistics and the JDBC statistics viewed from HTTP.APPLICATION SERVICE layer.

Last Invocation Panel

The last invocation panel serves as a way to track down the last five executions of the operations on the attached programs. The charts show the executions in terms of the total times and counts. Five sequences of the calls are shown under the last invocation panel. The panel allows the user to trace each of the calls. The below trace window shows the contents of a specific call executed.