eG Help

eG Monitoring

Weblogic Application dashboard

In order to ascertain how well an application is/has been performing, analysis of the performance of the System and Network layers of that application alone might not suffice. A closer look at the health of the Application Layers is also necessary, so as to promptly detect instantaneous operational issues with the target application, and also proactively identify persistent problems or a consistent performance degradation experienced by the application. To provide administrators with such in-depth insights into overall application performance and to enable them to accurately isolate the root-cause of any application-level slowdown, eG Enterprise offers the Application Dashboard. Each of the critical applications monitored by eG Enterprise is accompanied by an exclusive application dashboard. The contents of the dashboard will therefore primarily vary depending upon the application being monitored.

In addition, like the System and Network dashboards, the contents of the Application dashboard too are further governed by the Subsystem chosen from Application Dashboard. By default, the Overview option is chosen from the Subsystem list. If need be, you can change this default setting by picking a different option from the Subsystem list. The sections that follow will discuss each of the Subsystems offered by the sample WebLogic application dashboard.

Overview

The Overview dashboard of an WebLogic server provides an all-round view of the health of the WebLogic server being monitored, and helps administrators pinpoint the problem areas. Using this dashboard therefore, you can determine the following quickly and easily:

Is the application encountering any issue currently? If so, what is the issue and how critical is it?
How problem-prone has the application been during the last 24 hours? Which application layer has been badly hit?
Has the administrative staff been able to resolve all past issues? On an average, how long do the administrative personnel take to resolve an issue?
Are all the key performance parameters of the application operating normally?
What is the Application configuration of the WebLogic server?
What are the servlets invoked and reloaded by the WebLogic server? How quickly the servlets are being invoked and executed by the WebLogic server?
What are the instances of the EJB bean that are currently used from the free pool? How many threads are currently waiting per instance of the EJB group?
How well the EJB transaction activity is performed by the WebLogic server? How often the transactions are timed out by the bean in an EJB group?

The contents of the Overview Dashboard have been elaborated on hereunder:

The Current Application Alerts section of the Application Dashboard reveals the number and type of issues currently affecting the performance of the Oracle application that is being monitored. To know more about the current issues, click on any cell against Distribution that represents the problem priority of interest to you; the details of the current problems of that priority will then appear.

If the pop-up window of Current Application Alerts reveals too many problems, you can use the Search text boxes that have been provided at the end of the Description, Layer, and StartTime columns to run quick searches on the contents of these columns, so that the alarm of your interest can be easily located. For instance, to find the alarm with a specific description, you can provide the whole/part of the alarm description in the text box at the end of the Description column in the pop-up window of current application alerts; this will result in the automatic display of all the alarms with descriptions that contain the specified search string.

To zoom into the exact layer, test, and measure that reported any of the listed problems, click on a particular alarm in the Alarms window of the Current Application Alerts page. Doing so will introduce an Alarm Details section into the Alarms window, which provides the complete information related to the problem clicked on. These details include the Layer affected by the problem for which the alarm was raised, the test that reported the problem, and the last measure that was reported will be reported in the Last Measures.

While the list of current issues faced by the application serves as a good indicator of the current state of the application, to know how healthy/otherwise the application has been over time, a look at the problem history of the application is essential. Therefore, the dashboard provides the History of Events section; this section presents a bar chart, where every bar indicates the number of problems of a particular severity, which was experienced by the Oracle application during the last 1 hour (by default). Clicking on a bar here will lead you to the History of Alarms page which provides a detailed history of problems of that priority. Alongside the bar chart, you will also find a table displaying the average and maximum duration for problem resolution; this table helps you determine the efficiency of your administrative staff.

If required, you can override the default time period of 1 hour of the event history, by following the steps below:

Click the button at the top of the dashboard to invoke the Dashboard Settings window.
Select the Event History option from the Default timeline for list.
Set a different default timeline by selecting an option from the Timeline list.
Finally, click the Update button.

Back in the dashboard, you will find that the History of Events section is followed by an At-A-Glance section; this section, using pie charts, digital displays and gauge charts, reveals, at a single glance, the current status of some of the critical metrics and key components of the Oracle application. For instance, the Current Application Health pie chart indicates the current health of the application by representing the number of application-related metrics that are in various states. Clicking on a slice here will take you to History of Alarms page that provides a detailed problem history.

The dial and digital graphs that follow provide you with quick updates on the status of a pre-configured set of resource usage-related metrics pertaining to the Oracle application. If required, you can configure the dial graphs to display the threshold values of the corresponding measures along with their actual values, so that deviations can be easily detected. For this purpose, do the following:

Click the button at the top of the dashboard to invoke the Dashboard Settings window.
Set the Show Threshold in Dial Chart flag in the window to Yes.
Finally, click the Update button.

You can customize the At-A-Glance tab page further by overriding the default measure list for which dial/digital graphs are being displayed in that tab. To achieve this, do the following:

Click on the icon at the top of the Application Dashboard. In the Dashboard Settings window that appears, select Application from the Module list, and Overview from the Sub-System list.
To add measures for the dial graph, pick the Dial Graph option from the Add/Delete Measures for list. Upon selection of the Dial Graph option, the pre-configured measures for the dial graph will appear in the Existing Value(s) list. Similarly, to add a measure to the digital display, pick the Digital Graph option from the Add/Delete Measures for list. In this case, the Existing Value(s) list box will display all those measures for which digital displays pre-exist.
Next, select the Test that reports the said measure, pick the measure of interest from the Measures list, provide a Display name for the measure, and click the Add button to add the chosen measure to the Existing Value(s) list. Note that while configuring measures for a dial graph the ‘Measures’ list will display only those measures that report percentage values.
If you want to delete one/more measures from the dial/digital graphs, then, as soon as you choose the Dial Graph or Digital Graph option from the Add/Delete Measures for list, pick any of the displayed measures from the Existing Value(s) list, and click the Delete button.
Finally, click the Update button to register the changes.

Note:

Only users with Admin or Supermonitor privileges can enable/disable the system, network, and application dashboards, or can customize the contents of such dashboards using the Dashboard Settings window. Therefore, whenever a user without Admin or Supermonitor privileges logs into the monitoring console, the button will not appear.

Clicking on a dial/digital graph will lead you to the layer model page of the WebLogic server; this page will display the exact layer-test combination that reports the measure represented by the dial/digital graph.

If your eG license enables the Configuration Management capability, then, an Application Configuration section will appear here providing the basic configuration of the application. You can configure the type of configuration data that is to be displayed in this section by following the steps below:

Click on the icon at the top of the Application Dashboard. In the Dashboard Settings window that appears, select Application from the Module list, and Overview from the Sub-System list.
To add more configuration information to this section, first, pick the Application Configuration option from the Add/Delete Measures for list. Upon selection of this option, all the configuration measures that pre-exist in the Configuration Management section will appear in the Existing Value(s) list.
Next, select the config Test that reports the said measure, pick the measure of interest from the Measures list, provide a Display name for the measure, and click the Add button to add the chosen measure to the Existing Value(s) list.
If you want to delete one/more measures from this section, then, as soon as you choose the Application Configuration option from the Add/Delete Measures for list, pick any of the displayed measures from the Existing Value(s) list, and click the Delete button.
Finally, click the Update button to register the changes.

Next to this section, you will find a pre-configured list of Key Performance Indicators of the Oracle application. Besides indicating the current state of and current values reported by a default set of resource usage metrics, this section also reveals ‘miniature’ graphs of each measure, so that you can instantly study how that measure has behaved during the last 1 hour (by default) and thus determine whether the change in state of the measure was triggered by a sudden dip in performance or a consistent one. Clicking on a measure here in Application Dashboard of a WebLogic server will lead you to the Layer model page, which displays the layer and test that reports the measure.

You can, if required, override the default measure list in the Key Performance Indicators section by adding more critical measures to the list or by removing one/more existing ones from the list. For this, do the following:

Click on the icon at the top of the Application Dashboard. In the Dashboard Settings window that appears, select Application from the Module list, and Overview from the Sub-System list.
To add more metrics to the Key Performance Indicators section, first, pick the Performance Indicator option from the Add/Delete Measures for list. Upon selection of this option, all the measures that pre-exist in the Key Performance Indicators section will appear in the Existing Value(s) list.
Next, select the Test that reports the said measure, pick the measure of interest from the Measures list, provide a Display name for the measure, and click the Add button to add the chosen measure to the Existing Value(s) list.
If you want to delete one/more measures from this section, then, as soon as you choose the Key Performance Indicators option from the Add/Delete Measures for list, pick any of the displayed measures from the Existing Value(s) list, and click the Delete button.
Finally, click the Update button to register the changes.

Clicking on a ‘miniature’ graph that corresponds to a key performance indicator will enlarge the graph, so that you can view and analyze the measure behavior more clearly, and can also alter the Timeline and dimension (3D/ 2D) of the graph, if need be.

This way, the first few sections of the At-A-Glance tab page help understand what issues are currently affecting the application health, and when they actually originated. To diagnose the root-cause of these issues however, you would have to take help from the remaining sections of the At-A-Glance tab page. For instance, the Key Performance Indicators section may indicate a sudden/steady increase in the number of Inactive Connections of a user who is connected to the Oracle database. However, to determine whether the sudden rise in the number of Inactive Connections is due to the lack of availability of the Oracle database, you need to focus on the WebLogic Server Details section.

This WebLogic Server Details section for starters reveals the availability of the Oracle database and the other measures related to the availability of the Oracle database. With the help of this section, you can quickly figure out the following:

The response time taken by the database for a typical request;
The time period between when the connection was established and when the server sent back a HTTP response header to the client.
Was the TCP connection successfully established to the server?

WebLogic Server Details

The next section that is discussed in this Subsystem is the WebLogicJTA. This section focuses on the transaction related activity on the WebLogic server. Using this section, you will be able to figure out the following:

The number of active transactions on the server;
The rate at which the transactions were aborted on the server;
The rate of transactions that were rolled back due to an application error;
The rate of transactions that were rolled back due to a resource error;
The rate of transactions that were rolled back etc.,

Using this section you can easily identify the level of transaction activity on the WebLogic server and also identify which are the measures that are affecting the health of the WebLogic server.

The WebLogic Thread Pools section reveals on how well the self-tuning thread pool is utilized. This section reveals the total number of active threads in the thread pool, the number of threads that are currently ready to take up a new job process on the server, the number of threads that are currently in the standby pool, the number of requests in the priority queue that are completed., etc. This way, you can easily identify whether there are adequate idle threads to handle additional workload imposed on the WebLogic server.

The next section that is discussed in this Subsystem is the WebLogic Servlets. This section lists out the servlets that are invoked and reloaded on the WebLogic server. Using this section you can easily identify the following details for each servlet invoked/reloaded on the WebLogic server:

The average duration for which the single longest invocation of all the servlets within a servlet group executed since creation;
The average duration for which the single shortest invocation of all the servlets in a servlet group executed since creation;
The total number of times the servlets within a servlet group were invoked;
The total number of times for which the servlets within a servlet group were reloaded
The average response time of the servlets in a servlet group;

By default, the Servlet name list i.e., the name of the servlets in this section is sorted in the alphabetical order of the names of the servlets. If need be, you can change the sort order so that the servlets are arranged in, say, the descending order of values displayed in the Reloads of servlet column - this column displays the total number of times the servlets within a servlet group were reloaded. To achieve this, simply click on the column heading Reloads of servlet. Doing so tags the Reloads of servlet label with a down arrow icon - this icon indicates that the WebLogic Servlets table is currently sorted in the descending order of the total number of times the servlets were reloaded within a servlet group. To change the sort order to ‘ascending’, all you need to do is just click again on the Reloads of servlet label or the down arrow icon. Similarly, you can sort the table based on any column available in it. The WebLogic EJB Pools section in the Application Dashboard of a WebLogic server reveals how well the beans within an EJB group are utilized by the WebLogic server. With the help of this section, you can figure out the following regarding the beans in the EJB group:

The sum total of instances of every bean in an EJB group that are currently being used from the free pool;
The sum total of the instances of every bean within an EJB group that are currently available in the free pool;
The sum total of threads currently waiting for every available bean instance in an EJB group;
The sum total of the rate at which threads have timed out waiting for an available instance of every bean in an EJB group;
The sum total of the instances of every bean within an EJB group that are currently destroyed from the free pool;

By default, the Bean name list i.e., the name of the beans in this section is sorted in the alphabetical order of the names of the beans. If need be, you can change the sort order so that the beans are arranged in, say, the descending order of values displayed in the Idle beans column - this column displays the sum total of the instances of every bean within an EJB group that are currently available in the free pool. To achieve this, simply click on the column heading Idle beans. Doing so tags the Idle beans label with a down arrow icon - this icon indicates that the WebLogic EJB Pools table is currently sorted in the descending order of the total number of instances of the bean that are currently available in the free pool. To change the sort order to ‘ascending’, all you need to do is just click again on the Idle beans label or the down arrow icon. Similarly, you can sort the table based on any column available in it.

The WebLogic EJB Transactions section in the Application Dashboard of a WebLogic server reveals how well the EJB transaction activity is performed by the WebLogic server. With the help of this section, you can figure out the following regarding the transactions performed by the WebLogic server:

The rate at which the transactions are committed for a particular bean;
The rate at which the transactions are rolled back for a particular bean and
The rate at which the transactions are timed out by the bean

By default, the Bean name list i.e., the name of the beans in this section is sorted in the alphabetical order of the names of the beans. If need be, you can change the sort order so that the beans are arranged in, say, the descending order of values displayed in the Transaction rollbacks column - this column displays the sum total of the instances of every bean within an EJB group that are currently available in the free pool. To achieve this, simply click on the column heading Transaction rollbacks. Doing so tags the transaction rollbacks label with an up arrow icon - this icon indicates that the WebLogic EJB Transactions table is currently sorted in the ascending order of the rate at which the transactions are rolled back for a particular bean. To change the sort order to ‘descending’, all you need to do is just click again on the transaction rollbacks label or the up arrow icon. Similarly, you can sort the table based on any column available in it.

While the At-A-Glance tab page reveals the current state of the WebLogic server and the overall performance of the WebLogic server, to perform additional diagnosis on problem conditions highlighted by the At-A-Glance tab page and to accurately pinpoint their root-cause, you need to switch to the Details tab page by clicking on it. For instance, the At-A-Glance tab page may indicate the number of sessions that are currently open in the web application component on the WebLogic server, but to know the exact web application components that are responsible for the open sessions, you will have to use the Details tab page.

The Details tab page comprises of a default set of comparison bar graphs using which you can accurately determine the following:

What is the current size of the pending message that is stored in the queue destination of the WebLogic server?
How well the threads are utilized in a queue of the WebLogic server instance?
How many sessions are currently open for each web application component on the WebLogic server?
What is the rate at which the transactions are rolled back for a particular bean in an EJB group?
What is the rate at which the threads have timed out while waiting for an available instance of a bean in the EJB group?

If required, you can configure the Details tab page to include comparison graphs for more measures, or can even remove one/more existing graphs by removing the corresponding measures. To achieve this, do the following:

Click on the icon at the top of the Application Dashboard. In the Dashboard Settings window that appears, select Application from the Module list, and Overview from the Sub-System list.
To add measures for comparison graphs, first, pick the Comparison Graph option from the Add/Delete Measures for list. Upon selection of this option, the pre-configured measures for comparison graphs will appear in the Existing Value(s) list.
Next, select the Test that reports the said measure, pick the measure of interest from the Measures list, provide a Display name for the measure, and click the Add button to add the chosen measure to the Existing Value(s) list.
If you want to delete one/more measures for which comparison graphs pre-exist in the details tab page, then, as soon as you choose the Comparison Graph option from the Add/Delete Measures for list, pick any of the displayed measures from the Existing Value(s) list, and click the Delete button.
Finally, click the Update button to register the changes.

Note:

By default, the comparison bar graphs list the current usage of the top-10 tablespaces only. To view the complete list of tablespaces, simply click on the corresponding graph in Details tab page. This enlarges the Weblogic Threads by Utilization graph.

Though the enlarged graph lists all the databases in this case by default, you can customize the enlarged graph to display the details of only a few of the highest/lowest used tablespaces by picking a TOP-N or LAST-N option from the Show list of the Weblogic Threads by Utilization graph page.

Another default aspect of the enlarged graph is that it pertains to the current period only. Sometimes however, you might want to know what occurred during a point of time in the past; for instance, while trying to understand the reason behind a sudden increase or decrease in the current usage of the tablespace on a particular day last week, you might want to first determine the tablespace whose usage has abnormally increased / decreased on the same day. To figure this out, the enlarged graph allows you to compare the historical performance of the databases. For this purpose, click on the History link and select the TimeLine of your choice.

Where detailed diagnosis is applicable, you can quickly view the detailed measures that correspond to a comparison graph by clicking on the icon at the right, top corner of the enlarged graph.

For detailed time-of-day / trend analysis of the historical performance of a target Oracle database, use the History tab page. By default, this tab page provides time-of-day graphs of critical measures extracted from the target Oracle database, using which you can understand how performance has varied during the default period of 24 hours. In the event of a problem, these graphs will help you determine whether the problem occurred suddenly or grew with time. To alter the timeline of all the graphs simultaneously, click on the Timeline link at the right, top corner of the History tab page. Summary graphs will then appear.

You can even override the default timeline (of 24 hours) of the measure graphs, by following the steps below:

Click on the icon at the top of the Application Dashboard.
In the Dashboard Settings window that appears, select History Graph from the Default Timeline for list.
Then, choose a Timeline for the graph.
Finally, click the Update button.

You can click on any of the graphs to enlarge it, and can change the Timeline of that graph in the enlarged mode.

In case of tests that support descriptors, the enlarged graph will, by default, plot the values for the TOP-10 descriptors alone. To configure the graph to plot the values of more or less number of descriptors, select a different TOP-N / LAST-N option from the Show list.

If you want to quickly perform service level audits on the target WebLogic server, then summary graphs may be more appropriate than the default measure graphs. For instance, a summary graph might come in handy if you want to determine the variation of Total size of a tablespace with respect to the percentage of time during the last 24 hours. Using such a graph, you can determine whether the tablespace size has been constant or varied, and if not, how frequently the application faltered in this regard. To invoke such summary graphs, click on the icon at the right, top corner of the History tab page. An enlarged Summary graphs displayed in the History tab page of the Application Overview Dashboard.

You can alter the timeline of all the summary graphs at one shot by clicking the Timeline link at the right, top corner of the History tab page. You can even alter the default timeline (of 24 hours) for these graphs, by following the steps given below:

Click on the icon at the top of the Application Dashboard.
In the Dashboard Settings window that appears, select Summary Graph from the Default Timeline for list.
Then, choose a Timeline for the graph.
Finally, click the Update button.

To change the timeline of a particular graph, click on it; this will enlarge the summary graph. In the enlarged mode, you can alter the Timeline of the graph. Also, though the graph plots hourly summary values by default, you can pick a different Duration for the graph in the enlarged mode, so that daily/monthly performance summaries can be analyzed.

To perform effective analysis of the past trends in performance, and to accurately predict future measure behavior, click on the icon at the right, top corner of the History tab page. These trend graphs shows how well and how badly a measure has performed every hour during the last 24 hours (by default). For instance, the Total size Trend graphs displayed in the History tab page of the Application Overview Dashboard will help you figure out the total size of the tablespace that was available in the application every hour during the last 24 hours. If the gap between the minimum and maximum values is marginal, you can conclude that the size of the database has been more or less constant during the designated period; this implies that the size of the database has neither increased nor decreased steeply during the said timeline. On the other hand, a wide gap between the maximum and minimum values is indicative of an erratic change in the size of the database, and may necessitate further investigation.

To analyze trends over a broader time scale, click on the Timeline link at the right, top corner of the History tab page, and edit the Timeline of the trend graphs. Clicking on any of the miniature graphs in this tab page will enlarge that graph, so that you can view the plotted data more clearly and even change its Timeline.

To override the default timeline (of 24 hours) of the trend graphs, do the following:

Click on the icon at the top of the Application Dashboard.
In the Dashboard Settings window that appears, select Trend Graph from the Default Timeline for list.
Then, choose a Timeline for the graph.
Finally, click the Update button.

Besides the timeline, you can even change the Duration of the trend graph in the enlarged mode. By default, Hourly trends are plotted in the trend graph. By picking a different option from the Duration list, you can ensure that Daily or Monthly trends are plotted in the graph instead.

Also, by default, the trend graph only plots the minimum and maximum values registered by a measure. Accordingly, the Graph type is set to Min/Max in the enlarged mode. If need be, you can change the Graph type to Avg, so that the average trend values of a measure are plotted for the given Timeline. For instance, if an average trend graph is plotted for the Total size measure, then the resulting graph will enable administrators to ascertain whether the size of a particular database has been constant during a specified timeline.

Likewise, you can also choose Sum as the Graph type to view a trend graph that plots the sum of the values of a chosen measure for a specified timeline. For instance, if you plot a ‘sum of trends’ graph for the measure that reports the Total size of a tablespace available in the Oracle application, then, the resulting graph will enable you to analyze, on an hourly/daily/monthly basis (depending upon the Duration chosen), whether there was any change in the size of the tablespace.

Note:

In case of descriptor-based tests, the Summary and Trend graphs displayed in the History tab page typically plot the values for a single descriptor alone. To view the graph for another descriptor, pick a descriptor from the drop-down list made available above the corresponding summary/trend graph.

At any point in time, you can switch to the measure graphs by clicking on the button.
Typically, the History tab page displays measure, summary, and trend graphs for a default set of measures. If you want to add graphs for more measures to this tab page or remove one/more measures for which graphs pre-exist in this tab page, then, do the following:

Click the button at the top of the dashboard.
The Dashboard Settings window then appears. From the Module list of Dashbord settings page, pick Application, choose Overview as the Sub-System, and then, select History Graph from the Add/Delete Measures for list.
The measures for which graphs pre-exist in the History tab page will be automatically displayed in the Existing Value(s) list. To delete a measure, and in effect, its corresponding graph as well, select the measure from the Existing Value(s) list, click the Delete button, and then click the Update button.
To add a new graph, first, pick the Test that reports the measure for which a graph is to be generated.
Next, select the Measure of interest.
Provide a Display name for the measure. Then, click the Add button to add the measure to the Existing Values(s) list. Finally, click the Update button.
This will add a new measure, summary, and trend graph for the chosen measure, to the History tab page.

Note:

Only users with Admin or Supermonitor privileges can enable/disable the system, network, and application dashboards, or can customize the contents of such dashboards using the Dashboard Settings window. Therefore, whenever a user without Admin or Supermonitor privileges logs into the monitoring console, the button will not appear.

JVM

If you want to assess the performance of the WebLogic server's JVM, you can do so by analyzing the performance of the BEA JRockit JVM, the CPU utilization of the JVM from time to time; monitor the WebLogic thread usage in detail and thus promptly detect the server related discrepancies; select the JVM option from the Subsystem list.

The contents of the JVM Subsystem then appears are as follows:

The dashboard begins with a dial and digital graphs section, which enables you to visually track the changes that are happening in the measures related to the Oracle database. For instance, the number of locks that are held by the oracle database can be viewed at a single glance. Clicking on a dial/digital graph will lead you to the layer model page of the Oracle database; this page will display the exact layer-test combination that reports the measure represented by the dial/digital graph.

The At-A-Glance tab that follows will display a WebLogic RockitJVM Details section to view the critical measures related to the BEA Rockit JVM and a WebLogic JVM Details section will provide you with the details of the threads, CPU utilization of the JVM etc.

The WebLogic RockitJVM Details section helps you to visualize, how well the BEA Rockit JVM is performing in realtime. With the help of this section, you can easily figure out the following:

The percentage of Java heap memory that is currently used by the JRockit Virtual Machine (VM);
How well the Java heap memory has been utilized and how much of free heap memory is still available for utilization?
The number of times the garbage collection runs have occurred since the VM started and
The time the VM has spent on all garbage collection runs since the VM was started

By default, this section will display the performance of the BEA JKRockit JVM in digital graphs and a half-dial graph. Clicking on a graph will lead you to the layer model representation where you can view the exact layer and test that reports the measure.

The StackTrace tab page by default, displays the stack trace of each of the threads that are currently running on the JVM. Accordingly, the default selection in the Analysis By list is Runnable threads. To view the stack trace of those threads that are in a different state (say, Blocked, Waiting, Timed waiting, etc.), you will have to pick a different option from the Analysis By list.

A stack trace (also called stack backtrace or stack traceback) is a report of the active stack frames instantiated by the execution of a program. It is commonly used to determine what threads are currently active in the JVM, and which threads are in each of the different states - i.e., alive, blocked, waiting, timed waiting, etc.
Typically, when a Java application begins exhibiting erratic resource usage patterns, it often takes administrators hours, even days to figure out what is causing this anomaly - could it be owing to one/more resource-intensive threads being executed by the application? If so, what is causing the thread to erode resources? Is it an inefficient piece of code? In which case, which line of code could be the most likely cause for the spike in resource usage? To be able to answer these questions accurately, administrators need to know the complete list of threads that the application executes, view the stack trace of each thread, analyze each stack trace in a top-down manner, and trace where the problem originated.
The JVM Subsystem simplifies this seemingly laborious procedure by not only alerting administrators instantly to excessive resource usage by a thread, but also by providing the administrator with quick and easy access to the stack trace information of that thread; with the help of stack trace, administrators can effortlessly drill down to the exact line of code that requires optimization.

Regardless of the Analysis By option chosen, the thread list in the Thread Analysis section is sorted in the descending order of the percentage CPU time of the threads. We can thus conclude that the first thread for which stack trace is provided in this section is the top consumer of CPU. In the event of abnormally high CPU usage by this thread, you can use the stack trace to determine which line of code executed by this thread was causing the CPU usage to soar.

You will have to scroll down the Thread Analysis section to view the stack trace of the other threads. Alternatively, you can click on the icon next to the Analysis By list to invoke the Thread Analysis window using which you can quickly review the stack trace of each of the top CPU consumers.

Next to the StackTrace tab page is the Comparison tab page that displays a series of top-10 charts. These charts, by default, aid the quick and accurate identification of the thread that is currently consuming the maximum CPU, the thread that has been blocked for the longest time, and the thread that has been in waiting for the longest time.

If required, you can configure the Comparison tab page to include comparison graphs for more measures, or can even remove one/more existing graphs by removing the corresponding measures. To achieve this, do the following:

Click on the icon at the top of the Application Dashboard. In the Dashboard Settings window that appears, select Application from the Module list, and Overview from the Sub-System list.
To add measures for comparison graphs, first, pick the Comparison Graph option from the Add/Delete Measures for list. Upon selection of this option, the pre-configured measures for comparison graphs will appear in the Existing Value(s) list.
Next, select the Test that reports the said measure, pick the measure of interest from the Measures list, provide a Display name for the measure, and click the Add button to add the chosen measure to the Existing Value(s) list.
If you want to delete one/more measures for which comparison graphs pre-exist in the details tab page, then, as soon as you choose the Comparison Graph option from the Add/Delete Measures for list, pick any of the displayed measures from the Existing Value(s) list, and click the Delete button.
Finally, click the Update button to register the changes.

Note:

By default, the comparison bar graphs list the top-10 waiting threads only. To view the complete list of threads that are in waiting state, simply click on the corresponding graph in Comparison Tab Page. This enlarges the graph in the Comparison Tab Page.

Though the enlarged graph lists all the tablespaces in this case by default, you can customize the enlarged graph to display the details of only a few of the larger/smaller tablespaces by picking a TOP-N or LAST-N option from the Show list in the enlarged graph.

Another default aspect of the enlarged graph is that it pertains to the current period only. Sometimes however, you might want to know what occurred during a point of time in the past; for instance, while trying to understand the reason behind a sudden increase or decrease in the current hit ratio of the rollback segments (i.e., the ratio of waits to gets) on a particular day last week, you might want to first determine during which time period the current hit ratio has abnormally increased / decreased on the same day. To figure this out, the enlarged graph allows you to compare the historical performance of the rollback segments. For this purpose, click on the History link and select the TimeLine of your choice.

Where detailed diagnosis is applicable, you can quickly view the detailed measures that correspond to a comparison graph by clicking on the icon at the right, top corner of the enlarged graph. This will invoke the History Tab page, using which you can arrive at the root-cause of a problem.

Next to the Comparison tab, you will find the History tab that depicts how the server related measures such as the average lock time has been varying over time. In the event of any retaliation in the measures, this time-bound analysis will help you to easily differentiate between a normal lock time and a sudden rise in the same.
By default, these historical graphs track the time-of-day variations in memory usage during the last 24 hours. You can override this default timeline by following the steps discussed below:
- Click on the icon at the top of the Application Dashboard.
- In the Dashboard Settings window that appears, select History Graph from the Default Timeline for list.
- Then, choose a Timeline for the graph.
- Finally, click the Update button.

To change the timeline of all the measure graphs at one shot, just click on the Timeline link at the right, top corner of the History tab page. To alter the timeline for a single graph, just click on that graph - this will enlarge the graph. You can change the Timeline of the graph in the enlarged mode.

Instead of these measure graphs, you can, if required, view summary graphs of the memory-related measures in the History tab page. For this, click on the icon at the right, top corner of the History tab page. Summary graphs help you figure out the percentage of time during the last 24 hours (by default) the Oracle application was hogged by the server-related issues. While monitoring mission-critical applications that are governed by rigid service level agreements, summary graphs will help you determine whether the lock has been released within the specified time limit, and if not, how often the locks took too long to be released.

Click on the icon at the top of the Application Dashboard.
In the Dashboard Settings window that appears, select Summary Graph from the Default Timeline for list.
Then, choose a Timeline for the graph.
Finally, click the Update button.

Here again, you can change the Timeline of all the summary graphs by clicking on the Timeline link in the History tab page, or click on a graph, enlarge it, and change its Timeline in the enlarged mode. Also, though the graph plots hourly summary values by default, you can pick a different Duration for the graph in the enlarged mode, so that daily/monthly performance summaries can be analyzed.

You can click on the icon at the right, top corner of the History tab page to view trend graphs of the lock and segment-related measures. By default, these trend graphs plot the maximum and minimum values for every hour of the last 24 hours (by default).i.e., for e.g., the maximum and minimum value for the Heap usage percent measure will be plotted in this graph. The default timeline of 24 hours can be overridden by following the steps discussed below:
- Click on the icon at the top of the Application Dashboard.
- In the Dashboard Settings window that appears, select Trend Graph from the Default Timeline for list.
- Then, choose a Timeline for the graph.
- Finally, click the Update button.
Using these trend graphs, you can understand the variations that happened while the lock has been held in the Oracle database during the last 24 hours (by default), deduce the future lock trends, and accordingly recommend changes to the Oracle database.
Here again, you can change the Timeline of all the trend graphs by clicking on the Timeline link, or click on a graph, enlarge it, and change its Timeline in the enlarged mode. Also, though the graph plots hourly trend values by default, you can pick a different Duration for the graph in the enlarged mode, so that daily/monthly performance trends can be analyzed.
Also, by default, the trend graph only plots the minimum and maximum values registered by a measure. Accordingly, the Graph type is set to Min/Max in the enlarged mode. If need be, you can change the Graph type to Avg, so that the average trend values of a measure are plotted for the given Timeline. Such a graph will enable you to assess whether the memory resources were utilized effectively or not, over time.
Likewise, you can also choose Sum as the Graph type to view a trend graph that plots the sum of the values of a chosen measure for a specified timeline. For instance, a ‘sum of trends’ Avg Lock Wait will enable you to analyze, on an hourly/daily/monthly basis (depending upon the Duration chosen), how the locks have been held during the specified timeline.
Note:
In case of descriptor-based tests, the Summary and Trend graphs displayed in the History tab page typically plot the values for a single descriptor alone. To view the graph for another descriptor, pick a descriptor from the drop-down list made available above the corresponding summary/trend graph.
At any point in time, you can switch to the measure graphs by clicking on the button.
Typically, the History tab page displays measure, summary, and trend graphs for a default set of measures. If you want to add graphs for more measures to this tab page or remove one/more measures for which graphs pre-exist in this tab page, then, do the following:
- Click the button at the top of the dashboard.
- The Dashboard Settings window then appears. From the Module list, pick Application, choose JVM ures as the Sub-System, and then, select History Graph from the Add/Delete Measures for list.
- The measures for which graphs pre-exist in the History tab page will be automatically displayed in the Existing Value(s) list. To delete a measure, and in effect, its corresponding graph as well, select the measure from the Existing Value(s) list, click the Delete button, and then click the Update button.
- To add a new graph, first, pick the Test that reports the measure for which a graph is to be generated.
- Next, select the Measure of interest.
- Provide a Display name for the measure. Then, click the Add button to add the measure to the Existing Values(s) list. Finally, click the Update button.
- This will add a new measure, summary, and trend graph for the chosen measure to the History tab page.

Note:

WebLogic Threads

If you want to assess how well the threads in the Work Manager of the WebLogic server are utilized, and determine the availability of idle threads that are waiting to take up the job as and when required, select the WebLogic Threads option from the Subsystem list. This Subsystem also provides you with a clear insight on the Work Managers too. The WebLogic Server allows you to configure how your application prioritizes the execution of its work based on rules you define and by monitoring actual runtime performance. You define the rules and constraints for your application by defining a Work Manager and applying it either globally to the WebLogic Server domain or to a specific application component. This Subsystem thus helps you analyze how the Work Manager mapped to each application is managing the requests.

The contents of the Weblogic Threads Subsystem are discussed hereunder:

The dashboard begins with a dial and digital graphs section, which enables you to visually track the changes that are happening in the measures related to the size and usage of the tablespaces available in the WebLogic server. For instance, the Current usage of the tablespace you wish to view can be viewed at a single glance. Clicking on a dial/digital graph will lead you to the layer model page of the Oracle database; this page will display the exact layer-test combination that reports the measure represented by the dial/digital graph.

The At-A-Glance tab page displays critical measures related to the performance statistics pertaining to the thread pools of the WebLogic server. This page consists of two sections in tabular format namely, the WebLogic Threads and the WebLogic Work Managers.

The WebLogic Threads section in the WebLogic Dashboard reveals how well the threads executing on the Work Manager are utilized. With the help of this section i.e., this table, you can easily figure out the following:

The number of idle threads in a Work Manager that are readily available to take up a new job;
The percentage of threads that are utilized in a queue
The number of requests that are waiting in the queue and
The rate at which the requests are processed by the WebLogic Server

By default, the Thread Name list in this section lists out all the Work Managers associated with the WebLogic server. This list is by default, sorted in the alphabetical order of the names of the Work Managers. If need be, you can change the sort order so that the Work Managers are arranged in, say, the descending order of values displayed in the Pending requests column - this column displays the number of requests that are waiting to take up a job in the Work Manager. To achieve this, simply click on the column heading Pending requests. Doing so tags the Pending requests label with a down arrow icon - this icon indicates that the WebLogic Threads table is currently sorted in the ascending order of the number of requests that are waiting to take up a job in the Work Manager. To change the sort order to ‘descending’, all you need to do is just click again on the Pending requests label or the down arrow icon. Similarly, you can sort the table based on any column available in it.

The WebLogic Work Manager section in the WebLogic Dashboard reveals how well the requests to the applications are monitored and also helps you in analyzing how well the Work Manager mapped to each application is managing the requests. With the help of this section i.e., this table, you can easily figure out the following:

The number of requests that were successfully serviced by the Work Manager mapped to this web application;
The number of requests to this web application that are waiting in the queue and
The number of threads that are considered to be stuck due to any thread constraint

Work Manager

Pending requests

down arrow

WebLogic Threads

Pending requests

down arrow

The Comparison tab page displays a default set of comparison bar graphs using which you can accurately determine the following:
- The number of threads that are readily available to take up a job or work process.
- How well the threads are utilized in the Work Manager?
- The actual number of requests that are waiting in the queue.
- The number of requests to this application that are waiting in the queue.
- The number of threads that are considered to be stuck due to any thread constraint etc.,
If required, you can configure the Comparison tab page to include comparison graphs for more measures, or can even remove one/more existing graphs by removing the corresponding measures. To achieve this, do the following:
- Click on the icon at the top of the Application Dashboard. In the Dashboard Settings window that appears, select Application from the Module list, WebLogic Threads from the SubSystem list.
- To add measures for comparison graphs, first, pick the Comparison Graph option from the Add/Delete Measures for list. Upon selection of this option, the pre-configured measures for comparison graphs will appear in the Existing Value(s) list.
- Next, select the Test that reports the said measure, pick the measure of interest from the Measures list, provide a Display name for the measure, and click the Add button to add the chosen measure to the Existing Value(s) list.
- If you want to delete one/more measures for which comparison graphs pre-exist in the details tab page, then, as soon as you choose the Comparison Graph option from the Add/Delete Measures for list, pick any of the displayed measures from the Existing Value(s) list, and click the Delete button.
- Finally, click the Update button to register the changes.
Note:
Only users with Admin or Supermonitor privileges can enable/disable the system, network, and application dashboards, or can customize the contents of such dashboards using the Dashboard Settings window. Therefore, whenever a user without Admin or Supermonitor privileges logs into the monitoring console, the button will not appear.
By default, the comparison bar graphs list the top-10 tablespaces only. To view the complete list of tablespaces, simply click on the corresponding graph in Configuring measures for the dial graph. This enlarges the graph in the Details tab page.
Though the enlarged graph lists all the tablespaces in this case by default, you can customize the enlarged graph to display the details of only a few of the larger/smaller tablespaces by picking a TOP-N or LAST-N option from the Show list in the WebLogic Dashboard.
Another default aspect of the enlarged graph is that it pertains to the current period only. Sometimes however, you might want to know what occurred during a point of time in the past; for instance, while trying to understand the reason behind a sudden increase or decrease in the current hit ratio of the rollback segments (i.e., the ratio of waits to gets) on a particular day last week, you might want to first determine during which time period the current hit ratio has abnormally increased / decreased on the same day. To figure this out, the enlarged graph allows you to compare the historical performance of the tablespaces. For this purpose, click on the History link in the Application Dashboard and select the TimeLine of your choice.
Where detailed diagnosis is applicable, you can quickly view the detailed measures that correspond to a comparison graph by clicking on the icon at the right, top corner of the enlarged graph. This will invoke Time-of-day measure graphs displayed in the History tab page of the Application Overview Dashboard, using which you can arrive at the root-cause of a problem.
The History tab page displays time-of-day graphs for all the memory-related measures for a default time duration of 24 hours. You can override this default timeline (of 24 hours) by following the steps below:
- Click on the icon at the top of the Application Dashboard.
- In the Dashboard Settings window that appears, select History Graph from the Default Timeline for list.
- Then, choose a Timeline for the graph.
- Finally, click the Update button.
Say, you suddenly notice that the Physical Writes measure has increased; in such a case, you can use these measure graphs to figure out when during the last 24 hours there was an increase in the number of writes per sec in the tablespace. If required, you can even look beyond the last 24 hours - i.e., you can find out whether the anomaly originated much earlier. For this, you just need to click on the graph of interest to you. This will enlarge the graph; in the enlarged mode, you can alter the graph Timeline, so that the performance of that measure can be analyzed over a broader time window. In this mode, you can even change the graph dimension from 3D to 2D, or vice-versa.
To view summary graphs of these memory-related measures instead of the default measure graphs, just click on the icon at the right, top corner of the History tab page. The summary graph will then appear. The summary graph of the WebLogic Threads Subsystem reveal the percentage of time during the last 24 hours (by default) the tablespace of the Oracle database has been affected by usage related issues, and the type of issues (whether critical/major/minor) the application was experiencing. These graphs help determine whether the assured service levels were delivered or not.
The default duration (of 24 hours) of the summary graphs can be overridden by following the procedure discussed below:
- Click on the icon at the top of the Application Dashboard.
- In the Dashboard Settings window that appears, select Summary Graph from the Default Timeline for list.
- Then, choose a Timeline for the graph.
- Finally, click the Update button.
Use the Timeline link at the right, top corner of the tab page to change the timeline of all the summary graphs at one shot. For altering the timeline of a single graph, click on it; this will enlarge the graph. In the enlarged mode, you can change the Timeline of the summary graph and modify the dimension (3D/2D) of the graph. Also, by default, hourly summaries are plotted in the summary graph; you can configure these graphs to plot daily/monthly summaries instead by picking the relevant option from the Duration list in the enlarged mode.
If you want to view the past trends to know how many threads were available for each state in the Work Manager, click on the icon at the right, top corner of the History tab page. Trend graph will then appear. Using the trend graphs, you can better assess the current capacity of your Work Manager and can accordingly plan how effectively the threads can be utilized within a Work Manager. By default, these trend graphs plot the maximum and minimum values registered by every thread-related measure during every hour of the last 24 hours. From this data, you can clearly figure out when during the last 24 hours there were a considerable number of threads that were available to take up a job from the Work Manager.
The default duration (of 24 hours) of the trend graphs can be overridden by following the procedure discussed below:
- Click on the icon at the top of the Application Dashboard.
- In the Dashboard Settings window that appears, select Trend Graph from the Default Timeline for list.
- Then, choose a Timeline for the graph.
- Finally, click the Update button.
Use the Timeline link at the right, top corner of the tab page to change the timeline of all the trend graphs at one shot. For altering the timeline of a single graph, click on it; this will enlarge the graph. In the enlarged mode, you can change the Timeline of the trend graph and modify the dimension (3D/2D) of the graph. Also, by default, hourly trends are plotted in the trend graph; you can configure these graphs to plot daily/monthly trend values instead by picking the relevant option from the Duration list in the enlarged mode. Moreover, by default, the trend graphs plot only the minimum and maximum values registered by a measure during the specified timeline - this graph will enable you to isolate those times at which performance of that measure had peaked and the times it had fared poorly. If need be, you can select the Avg option from the Graph type list in the enlarged mode to make sure that the trend graph plots the average trend values for the specified timeline. Alternatively, you can select the Sum option from the Graph type list to have the trend graph plot the sum of trends for the specified timeline.
Note:
In case of descriptor-based tests, the Summary and Trend graphs displayed in the History tab page typically plot the values for a single descriptor alone. To view the graph for another descriptor, pick a descriptor from the drop-down list made available above the corresponding summary/trend graph.
At any point in time, you can switch to the measure graphs by clicking on the button.
Typically, the History tab page displays measure, summary, and trend graphs for a default set of measures. If you want to add graphs for more measures to this tab page or remove one/more measures for which graphs pre-exist in this tab page, then, do the following:
- Click the button at the top of the dashboard.
- The Dashboard Settings window then appears. From the Module list, pick Application, choose Weblogic Threads as the Sub-System, and then, select History Graph from the Add/Delete Measures for list.
- The measures for which graphs pre-exist in the History tab page will be automatically displayed in the Existing Value(s) list. To delete a measure, and in effect, its corresponding graph as well, select the measure from the Existing Value(s) list, click the Delete button, and then click the Update button.
- To add a new graph, first, pick the Test that reports the measure for which a graph is to be generated.
- Next, select the Measure of interest.
- Provide a Display name for the measure. Then, click the Add button to add the measure to the Existing Values(s) list. Finally, click the Update button.
- This will add a new measure, summary, and trend graph for the chosen measure to the History tab page.
Note:
Only users with Admin or Supermonitor privileges can enable/disable the system, network, and application dashboards, or can customize the contents of such dashboards using the Dashboard Settings window. Therefore, whenever a user without Admin or Supermonitor privileges logs into the monitoring console, the button will not appear.

Weblogic service

Select the Weblogic service option from the Subsystem list to know how efficiently the information stored in the datafiles of the Oracle database is accessed. Upon selection, The Weblogic service Subsystem will appear.

The contents of this Weblogic service Subsystem are as follows:

The dashboard begins with a pre-configured dial and digital graphs section, which enables you to visually track the availability of the server, the rate at which the transactions were rolled back due to an application error etc, at a single glance. Clicking on a dial/digital graph will lead you to the layer model page of the WebLogic server; this page will display the exact layer-test combination that reports the measure represented by the dial/digital graph.

The At-A-Glance tab page displays critical measures that reveal how healthy the Weblogic service layer of the WebLogic server is? This page consists of four different sections in tabular format namely, the WebLogic Servlets, WebLogic Web Applications, WebLogic Queue and the WebLogic Topic.

The WebLogic Servlets section in the Application Dashboard reveals a pre-configured set of metrics relating to how well the servlets are invoked, executed and reloaded on the WebLogic server. With the help of this section i.e., this table, you can easily figure out the following:

What is the maximum/minimum/average execution time of the WebLogic servlet;
How many times the servlets in a servlet group have been reloaded?
How many times the servlets in a servlet group have been invoked?

By default, the Bean name list in this section lists out all the servlets that are currently loaded on the WebLogic server. This list is by default, sorted in the alphabetical order of the names of the servlets. If need be, you can change the sort order so that the servlets are arranged in, say, the descending order of values displayed in the Max execution time of servlet column - this column displays the average duration for which the single longest invocation of all the servlets within a servlet group executed since creation. To achieve this, simply click on the column heading Max execution time of servlet. Doing so tags the Max execution time of servlet label with a down arrow icon - this icon indicates that the WebLogic Servlets table is currently sorted in the ascending order of the duration of the longest invocation of the servlet since creation. To change the sort order to ‘descending’, all you need to do is just click again on the Max execution time of servlet label or the down arrow icon. Similarly, you can sort the table based on any column available in it.

The WebLogic Web Applications section in the Application Dashboard reveals a pre-configured set of metrics relating to the performance data of each of the web application component deployed on the WebLogic server. With the help of this section i.e., this table, you can easily figure out the following:

How many sessions are currently open for each web application component currently?
How many high water mark sessions are currently open in each web application component?
How many sessions are open for each web application component since the last measurement period?
What is the invalidation check timer interval that is configured for the HTTP sessions for each of the web application in the WebLogic server?

By default, the Web Application list in this section lists out all the web application components that are currently deployed on the WebLogic server. This list is by default, sorted in the alphabetical order of the names of the web applications. If need be, you can change the sort order so that the web applications are arranged in, say, the descending order of values displayed in the Sessions open current column - this column displays the number of sessions that are currently open for each of the web application deployed on the WebLogic server. To achieve this, simply click on the column heading Sessions open current. Doing so tags the Sessions open current label with a down arrow icon - this icon indicates that the WebLogic Web Applications table is currently sorted in the ascending order of the number of currently open sessions in each web application. To change the sort order to ‘descending’, all you need to do is just click again on the Sessions open current label or the down arrow icon. Similarly, you can sort the table based on any column available in it.

The Weblogic Queue section in the Application Dashboard reveals a pre-configured set of metrics relating to the queues on the WebLogic server. With the help of this section i.e., this table, you can easily figure out the following:

How many messages are there in each queue?
How many messages are pending in each queue?
The size of the messages in each queue according to their type
The number of messages that are deleted from each queue
The number of consumers currently accessing each queue

By default, the Queue list in this section lists out all the queues in the WebLogic server. This list is by default, sorted in the alphabetical order of the names of the queues. If need be, you can change the sort order so that the queues are arranged in, say, the descending order of values displayed in the Consumers count column - this column displays the number of consumers who are currently accessing each queue in the WebLogic server. To achieve this, simply click on the column heading Consumers count. Doing so tags the Consumers count label with a down arrow icon - this icon indicates that the WebLogic Queue table is currently sorted in the ascending order of the number of consumers currently accessing each queue. To change the sort order to ‘descending’, all you need to do is just click again on the Consumers count label or the down arrow icon. Similarly, you can sort the table based on any column available in it.

The WebLogic Topic section in the Application Dashboard reveals a pre-configured set of metrics relating to the topics on the WebLogic server. With the help of this section i.e., this table, you can easily figure out the following:

How many messages are there in each topic?
How many messages are pending in each topic?
The size of the messages in each topic according to their type
The number of messages that are deleted from each topic
The number of consumers currently accessing each topic

By default, the Topic list in this section lists out all the topics on the WebLogic server. This list is by default, sorted in the alphabetical order of the names of the topics. If need be, you can change the sort order so that the topics are arranged in, say, the descending order of values displayed in the Consumers count column - this column displays the number of consumers who are currently accessing each topic destination on the WebLogic server. To achieve this, simply click on the column heading Consumers count. Doing so tags the Consumers count label with a down arrow icon - this icon indicates that the WebLogic Topic table is currently sorted in the ascending order of the number of consumers currently accessing each topic. To change the sort order to ‘descending’, all you need to do is just click again on the Consumers count label or the down arrow icon. Similarly, you can sort the table based on any column available in it.

The Comparison tab page provides a series of top 10 charts, using which you can identify the top average execution time of the servlets that are executing on the WebLogic server, the top-10 queues in terms of the total number of messages etc., This default list of measures for top-n chart generation can be overridden by following the steps discussed below:
- Click on the icon at the top of the Application Dashboard. In the Dashboard Settings window that appears, select Application from the Module list, and Weblogic service from the Sub-System list.
- To add new measures for which top-n graphs are to be displayed in the Comparison tab page, first, pick the Comparison Graph option from the Add/Delete Measures for list. Upon selection of this option, the pre-configured measures for comparison graphs will appear in the Existing Value(s) list.
- Next, select the Test that reports the said measure, pick the measure of interest from the Measures list, provide a Display name for the measure, and click the Add button to add the chosen measure to the Existing Value(s) list.
- If you want to delete one/more measures for which comparison graphs pre-exist in the Comparison tab page, then, as soon as you choose the Comparison Graph option from the Add/Delete Measures for list, pick any of the displayed measures from the Existing Value(s) list, and click the Delete button.
- Finally, click the Update button to register the changes.
Note:
Only users with Admin or Supermonitor privileges can enable/disable the system, network, and application dashboards, or can customize the contents of such dashboards using the Dashboard Settings window. Therefore, whenever a user without Admin or Supermonitor privileges logs into the monitoring console, the button will not appear.

To view the complete list of web applications that are deployed on the WebLogic server, simply click on the corresponding graph. This enlarges the Comparison graph.

Though the enlarged graph lists all the web applications, by default, you can customize the enlarged graph to display the details of only a few of the highest/lowest count of the current open sessions by picking a TOP-N or LAST-N option from the Show list in the Application Tab page.

Another default aspect of the enlarged graph is that it pertains to the current period only. Sometimes however, you might want to know what occurred during a point of time in the past; for instance, while trying to understand the reason behind an abnormal activity in the total I/O of a particular datafile on a particular day last week, you might want to first determine which datafile has behaved abnormally on the same day. To figure this out, the enlarged graph allows you to compare the historical performance of the datafiles. For this purpose, click on the History link in the Application Tab page and select the TimeLine of your choice.

The History tab page below, by default, provides a series of measure graphs that reveal how the well the I/O related activity has been happening in each datafile over the default duration of the last 24 hours. If there is a sudden slowdown in the I/O related activity, it could indicate that the Oracle database is experiencing issues with the blocks of the datafiles. In such a case, a look at these measure graphs will help you figure out when exactly the bottleneck surfaced - did it happen suddenly or is it a condition that has become worse with time?

The default duration of 24 hours can be overridden using the procedure discussed below:

Click on the icon at the top of the Application Dashboard.
In the Dashboard Settings window that appears, select History Graph from the Default Timeline for list.
Then, choose a Timeline for the graph.
Finally, click the Update button.

Note:

If need be, you can even alter the timeline of all these measure graphs so that you can analyze performance across days and weeks; for this, simply click the Timeline link at the right, top corner of the History tab page and change the timeline for the graphs using the calendar that pops out. To change the timeline of a single graph alone, simply click on that graph to enlarge it, and then modify the Timeline of the graph in the enlarged mode. In the enlarged mode, you can even change the dimension of the measure graph (3D / 2D).

To determine the service level achievements / slippages happened in each of the datafile, you need to view summary graphs of the measures and not the default measure graphs. For this, just click on the icon at the right, top corner of the History tab page.

The summary graphs reveal the percentage of time the datafile experienced problems in the database. Besides revealing the efficiency of your administrative staff in recognizing bottlenecks and mitigating them, these summary graphs also indicate whether the datafile has been able to maintain the assured performance levels during the default duration of 24 hours.
To override this default duration, follow the steps below:
- Click on the icon at the top of the Application Dashboard.
- In the Dashboard Settings window that appears, select Summary Graph from the Default Timeline for list.
- Then, choose a Timeline for the graph.
- Finally, click the Update button.
In case of the summary graphs too, you can change the Timeline of all graphs by clicking on the Timeline link at the right, top corner of the History tab page. To alter the timeline of a single graph, here again, you will have to click on that graph, enlarge it, and modify the timeline. Also, by default, hourly summaries are plotted in the summary graph; you can configure these graphs to plot daily/monthly summaries instead by picking the relevant option from the Duration list in the enlarged mode.
To analyze past trends in the behavior of the datafiles, click on the icon at the right, top corner of the History tab page. These trend graphs, by default, plot the minimum and maximum values that every measure registered during each hour of the last 24 hours (by default). By carefully observing these past trends, you can effectively analyze the workload of the datafile, predict future workloads accordingly, and suggest measures to enhance the efficiency of the datafile. Here again, you can change the timeline of all graphs using the Timeline link, or just a particular graph by clicking on it and enlarging it.
For changing the default duration (of 24 hours) of the trend graphs, do the following:
- Click on the icon at the top of the Application Dashboard.
- In the Dashboard Settings window that appears, select Trend Graph from the Default Timeline for list.
- Then, choose a Timeline for the graph.
- Finally, click the Update button.
In addition, when a trend graph is enlarged, it is not just the Timeline that you can modify. The Duration of the graph can also be altered. By default, trend graphs reveal only the hourly trends in performance. By picking the relevant option from the Duration list, you can ensure that the trend graph in question plots daily/monthly trend values instead. Also, in the enlarged mode, the Graph type can also be modified. Since the default Graph type is Min/Max, the trend graph, by default, reveals the minimum and maximum values registered by a measure. If need be, you can select the Avg or Sum option from the Graph type list to plot average trend values of a measure or sum of trends (as the case may be) in the graph.
Note:
In case of descriptor-based tests, the Summary and Trend graphs displayed in the History tab page typically plot the values for a single descriptor alone. To view the graph for another descriptor, pick a descriptor from the drop-down list made available above the corresponding summary/trend graph.
At any point in time, you can switch to the measure graphs by clicking on the button.
Typically, the History tab page displays measure, summary, and trend graphs for a default set of measures. If you want to add graphs for more measures to this tab page or remove one/more measures for which graphs pre-exist in this tab page, then, do the following:
- Click the button at the top of the dashboard.
- The Dashboard Settings window then appears. From the Module list, pick Application, choose Weblogic service as the Sub-System, and then, select History Graph from the Add/Delete Measures for list.
- The measures for which graphs pre-exist in the History tab page will be automatically displayed in the Existing Value(s) list. To delete a measure, and in effect, its corresponding graph as well, select the measure from the Existing Value(s) list, click the Delete button, and then click the Update button.
- To add a new graph, first, pick the Test that reports the measure for which a graph is to be generated.
- Next, select the Measure of interest.
- Provide a Display name for the measure. Then, click the Add button to add the measure to the Existing Values(s) list. Finally, click the Update button.
- This will add a new measure, summary, and trend graph for the chosen measure to the History tab page.
Note:
Only users with Admin or Supermonitor privileges can enable/disable the system, network, and application dashboards, or can customize the contents of such dashboards using the Dashboard Settings window. Therefore, whenever a user without Admin or Supermonitor privileges logs into the monitoring console, the button will not appear.

WebLogic databases

Select the WebLogic databases option from the Subsystem list to know how well the Oracle database has been responding to the service request from the client applications. Upon selection of this Subsystem, the At-A-Glance tab page of the Weblogic databases Subsystem will appear.

The contents of the Weblogic databases Subsystem are as follows:

This Subsystem begins with a dial and digital graphs section, which enables you to visually track the changes that are happening in the measures related to the availability of the database pool and the numerical statistics relating to various states of the connections in the database pool. For instance, you can view the Active connections max measure i.e., the high water mark of active connections in a database pool, at a single glance. Clicking on a dial/digital graph will lead you to the layer model page of the WebLogic server; this page will display the exact layer-test combination that reports the measure represented by the dial/digital graph.

The At-A-Glance tab page provides database related statistics pertaining to the WebLogic server in a more elaborate manner. This way you could better be aware of each minute data related to the backend database server - in other words the database pools that are created on the WebLogic server. This tab page is divided into two sections - the left panel and the right panel separated by a left arrow button. The left panel lists out all the Data Source i.e., the database pools created on the WebLogic server, in a tree format. Upon selecting a data source from the tree structure, the context sensitive right panel will display a pre-configured set of digital graphs that provides a single glance view of the numerical statistics regarding the state of the connections from the database connection pool. Clicking on a digital graph will lead you to the layer model page of the WebLogic server; this page will display the exact layer-test combination that reports the measure represented by the digital graph.

The Comparison tab page that follows the Top Queries tab page provides a series of top-10 charts, using which you can isolate the users and sessions that are leading the lot in the following fields: total connections, active connections, average wait time of the session etc., This default list of fields (i.e., measures) for top-n chart generation can be overridden by following the steps discussed below:
- Click on the icon at the top of the Application Dashboard. In the Dashboard Settings window that appears, select Application from the Module list, and Weblogic databases from the Sub-System list.
- To add new measures for which top-n graphs are to be displayed in the Comparison tab page, first, pick the Comparison Graph option from the Add/Delete Measures for list. Upon selection of this option, the pre-configured measures for comparison graphs will appear in the Existing Value(s) list.
- Next, select the Test that reports the said measure, pick the measure of interest from the Measures list, provide a Display name for the measure, and click the Add button to add the chosen measure to the Existing Value(s) list.
- If you want to delete one/more measures for which comparison graphs pre-exist in the Comparison tab page, then, as soon as you choose the Comparison Graph option from the Add/Delete Measures for list, pick any of the displayed measures from the Existing Value(s) list, and click the Delete button.
- Finally, click the Update button to register the changes.

Note:

For example, to view the top JDBC pools possessing active connections, simply click on the corresponding graph in the Comparision tab. This enlarges the graph in the Comparison tab page

Though the enlarged graph lists all the databases by default, you can customize the enlarged graph to display the details of only a few of the best/worst-performing databases by picking a TOP-N or LAST-N option from the Show list in the enlarged graph of the Comparison tab page.

Another default aspect of the enlarged graph is that it pertains to the current period only. Sometimes however, you might want to know what occurred during a point of time in the past; for instance, while trying to understand the reason behind a sudden decrease in the number of active connections of the chosen user on a particular day last week, you might want to first determine what was the cause for this abnormal behavior on the same day. To figure this out, the enlarged graph allows you to compare the historical performance of users. For this purpose, click on the History link Comparison tab page and select the TimeLine of your choice.

The History tab page below, by default, provides a series of measure graphs that reveal for example, how well the users are connected to the Oracle database over the default duration of the last 24 hours. If there is a sudden decrease in the number of active connections, it could indicate that there is some performance issue with the connectivity of the oracle database. In such a case, a look at these measure graphs will help you figure out when exactly the bottleneck surfaced - did it happen suddenly or is it a condition that has become worse with time?

The default duration of 24 hours can be overridden using the procedure discussed below:

Click on the icon at the top of the Application Dashboard.
In the Dashboard Settings window that appears, select History Graph from the Default Timeline for list.
Then, choose a Timeline for the graph.
Finally, click the Update button.

Note:

If need be, you can even alter the timeline of all these measure graphs so that you can analyze performance across days and weeks; for this, simply click the Timeline link at the right, top corner of the History tab page and change the timeline for the graphs using the calendar that pops out. To change the timeline of a single graph alone, simply click on that graph to enlarge it, and then modify the Timeline of the graph in the enlarged mode. Though the enlarged graph lists all the databases by default, you can customize the enlarged graph to display the details of only a few of the best/worst-performing databases by picking a TOP-N or LAST-N option from the Show list. In the enlarged mode, you can even change the dimension of the measure graph (3D / 2D).

To determine the service level achievements of the connection related activity between the database connection pool and the WebLogic server, you need to view summary graphs of the measures and not the default measure graphs. For this, just click on the icon at the right, top corner of the History tab page. The summary graphs reveal the percentage of time the database connection pool experienced problems connectivity issues with the WebLogic server. Besides revealing the efficiency of your administrative staff in recognizing bottlenecks and mitigating them, these summary graphs also indicate whether the data sources i.e., the database connection pools were able to maintain the assured performance levels with the WebLogic server during the default duration of 24 hours.
To override this default duration, follow the steps below:
- Click on the icon at the top of the Application Dashboard.
- In the Dashboard Settings window that appears, select Summary Graph from the Default Timeline for list.
- Then, choose a Timeline for the graph.
- Finally, click the Update button.
In case of the summary graphs too, you can change the Timeline of all graphs by clicking on the Timeline link at the right, top corner of the History tab page. To alter the timeline of a single graph, here again, you will have to click on that graph, enlarge it, and modify the timeline. Also, by default, hourly summaries are plotted in the summary graph; you can configure these graphs to plot daily/monthly summaries instead by picking the relevant option from the Duration list in the enlarged mode.
To analyze past trends in the performance of the databases, click on the icon at the right, top corner of the History tab page. The History tab page of the Database access Subsystem will then appear.
These trend graphs, by default, plot the minimum and maximum values that every measure registered during each hour of the last 24 hours (by default). Using such graphs, you can accurately point to the time windows during which there was a lull in the active connections for the chosen user in the Oracle database. Here again, you can change the timeline of all graphs using the Timeline link, or just a particular graph by clicking on it and enlarging it.
For changing the default duration (of 24 hours) of the trend graphs, do the following:
- Click on the icon at the top of the Application Dashboard.
- In the Dashboard Settings window that appears, select Trend Graph from the Default Timeline for list.
- Then, choose a Timeline for the graph.
- Finally, click the Update button.
In addition, when a trend graph is enlarged, it is not just the Timeline that you can modify. The Duration of the graph can also be altered. By default, trend graphs reveal only the hourly trends in performance. By picking the relevant option from the Duration list, you can ensure that the trend graph in question plots daily/monthly trend values instead. Also, in the enlarged mode, the Graph type can also be modified. Since the default Graph type is Min/Max, the trend graph, by default, reveals the minimum and maximum values registered by a measure. If need be, you can select the Avg or Sum option from the Graph type list to plot average trend values of a measure or sum of trends (as the case may be) in the graph.
Note:
In case of descriptor-based tests, the Summary and Trend graphs displayed in the History tab page typically plot the values for a single descriptor alone. To view the graph for another descriptor, pick a descriptor from the drop-down list made available above the corresponding summary/trend graph.
At any point in time, you can switch to the measure graphs by clicking on the button.
Typically, the History tab page displays measure, summary, and trend graphs for a default set of measures. If you want to add graphs for more measures to this tab page or remove one/more measures for which graphs pre-exist in this tab page, then, do the following:
- Click the button at the top of the dashboard.
- The Dashboard Settings window then appears. From the Module list, pick Application, choose Database access as the Sub-System, and then, select History Graph from the Add/Delete Measures for list.
- The measures for which graphs pre-exist in the History tab page will be automatically displayed in the Existing Value(s) list. To delete a measure, and in effect, its corresponding graph as well, select the measure from the Existing Value(s) list, click the Delete button, and then click the Update button.
- To add a new graph, first, pick the Test that reports the measure for which a graph is to be generated.
- Next, select the Measure of interest.
- Provide a Display name for the measure. Then, click the Add button to add the measure to the Existing Values(s) list. Finally, click the Update button.
- This will add a new measure, summary, and trend graph for the chosen measure to the History tab page.
Note:
Only users with Admin or Supermonitor privileges can enable/disable the system, network, and application dashboards, or can customize the contents of such dashboards using the Dashboard Settings window. Therefore, whenever a user without Admin or Supermonitor privileges logs into the monitoring console, the button will not appear.

WebLogic EJB

The contents of this Subsystem are as follows:

The Subsystem begins with a dial and digital graphs section, which enables you to visually track the changes that are happening in the measures related to the caching activity on the WebLogic server, rate at which the locks are held in each bean of the EJB Group, the rate at which the transactions are timed out by the bean etc., For instance, you can view the EJB Passivation rate measure i.e., the rate at which every bean from a specific EJB bean have been passivated, at a single glance. Clicking on a dial/digital graph will lead you to the layer model page of the WebLogic server; this page will display the exact layer-test combination that reports the measure represented by the dial/digital graph.

The Comparison tab page that follows the Top Queries tab page provides a series of top-10 charts, using which you can isolate the users and sessions that are leading the lot in the following fields: total connections, active connections, average wait time of the session etc.,. This default list of fields (i.e., measures) for top-n chart generation can be overridden by following the steps discussed below:
- Click on the icon at the top of the Application Dashboard. In the Dashboard Settings window that appears, select Application from the Module list, and Weblogic databases from the Sub-System list.
- To add new measures for which top-n graphs are to be displayed in the Comparison tab page, first, pick the Comparison Graph option from the Add/Delete Measures for list. Upon selection of this option, the pre-configured measures for comparison graphs will appear in the Existing Value(s) list.
- Next, select the Test that reports the said measure, pick the measure of interest from the Measures list, provide a Display name for the measure, and click the Add button to add the chosen measure to the Existing Value(s) list.
- If you want to delete one/more measures for which comparison graphs pre-exist in the Comparison tab page, then, as soon as you choose the Comparison Graph option from the Add/Delete Measures for list, pick any of the displayed measures from the Existing Value(s) list, and click the Delete button.
- Finally, click the Update button to register the changes.

Note:

For example, to view the top instances of beans in an EJB group that are currently being used from the free pool, simply click on the corresponding graph in the Comparison tab page. This enlarges the graph of the Weblogic EJB Subsystem

Though the enlarged graph lists all the databases by default, you can customize the enlarged graph to display the details of only a few of the best/worst-performing databases by picking a TOP-N or LAST-N option from the Show list in the Comparison tab page.

Another default aspect of the enlarged graph is that it pertains to the current period only. Sometimes however, you might want to know what occurred during a point of time in the past; for instance, while trying to understand the reason behind a sudden decrease in the number of active connections of the chosen user on a particular day last week, you might want to first determine what was the cause for this abnormal behavior on the same day. To figure this out, the enlarged graph allows you to compare the historical performance of users. For this purpose, click on the History link in the Application Dashboard and select the TimeLine of your choice.

The History tab page below, by default, provides a series of measure graphs that reveal for example, how well the users are connected to the Oracle database over the default duration of the last 24 hours. If there is a sudden decrease in the number of active connections, it could indicate that there is some performance issue with the connectivity of the oracle database. In such a case, a look at these measure graphs will help you figure out when exactly the bottleneck surfaced - did it happen suddenly or is it a condition that has become worse with time?

The default duration of 24 hours can be overridden using the procedure discussed below:

Click on the icon at the top of the Application Dashboard.
In the Dashboard Settings window that appears, select History Graph from the Default Timeline for list.
Then, choose a Timeline for the graph.
Finally, click the Update button.

Note:

To determine the service level achievements of the user and session related activity of the Oracle database, you need to view summary graphs of the measures and not the default measure graphs. For this, just click on the icon at the right, top corner of the History tab page. The Comparison tab page of the Database access Subsystem then appears.
The summary graphs displayed reveals the percentage of time the oracle database experienced problems with user connections and session related activities. Besides revealing the efficiency of your administrative staff in recognizing bottlenecks and mitigating them, these summary graphs also indicate whether the users were able to maintain the assured performance levels with the database during the default duration of 24 hours.
To override this default duration, follow the steps below:
- Click on the icon at the top of the Application Dashboard.
- In the Dashboard Settings window that appears, select Summary Graph from the Default Timeline for list.
- Then, choose a Timeline for the graph.
- Finally, click the Update button.
In case of the summary graphs too, you can change the Timeline of all graphs by clicking on the Timeline link at the right, top corner of the History tab page. To alter the timeline of a single graph, here again, you will have to click on that graph, enlarge it, and modify the timeline. Also, by default, hourly summaries are plotted in the summary graph; you can configure these graphs to plot daily/monthly summaries instead by picking the relevant option from the Duration list in the enlarged mode.
To analyze past trends in the performance of the databases, click on the icon at the right, top corner of the History tab page. The History tab page of the Database access Subsystem will then appear.
These trend graphs, by default, plot the minimum and maximum values that every measure registered during each hour of the last 24 hours (by default). Using such graphs, you can accurately point to the time windows during which there was a lull in the active connections for the chosen user in the Oracle database. Here again, you can change the timeline of all graphs using the Timeline link, or just a particular graph by clicking on it and enlarging it.
For changing the default duration (of 24 hours) of the trend graphs, do the following:
- Click on the icon at the top of the Application Dashboard.
- In the Dashboard Settings window that appears, select Trend Graph from the Default Timeline for list.
- Then, choose a Timeline for the graph.
- Finally, click the Update button.
In addition, when a trend graph is enlarged, it is not just the Timeline that you can modify. The Duration of the graph can also be altered. By default, trend graphs reveal only the hourly trends in performance. By picking the relevant option from the Duration list, you can ensure that the trend graph in question plots daily/monthly trend values instead. Also, in the enlarged mode, the Graph type can also be modified. Since the default Graph type is Min/Max, the trend graph, by default, reveals the minimum and maximum values registered by a measure. If need be, you can select the Avg or Sum option from the Graph type list to plot average trend values of a measure or sum of trends (as the case may be) in the graph.
Note:
In case of descriptor-based tests, the Summary and Trend graphs displayed in the History tab page typically plot the values for a single descriptor alone. To view the graph for another descriptor, pick a descriptor from the drop-down list made available above the corresponding summary/trend graph.
At any point in time, you can switch to the measure graphs by clicking on the button.
Typically, the History tab page displays measure, summary, and trend graphs for a default set of measures. If you want to add graphs for more measures to this tab page or remove one/more measures for which graphs pre-exist in this tab page, then, do the following:
- Click the button at the top of the dashboard.
- The Dashboard Settings window then appears. From the Module list, pick Application, choose WebLogic EJB as the Sub-System, and then, select History Graph from the Add/Delete Measures for list.
- The measures for which graphs pre-exist in the History tab page will be automatically displayed in the Existing Value(s) list. To delete a measure, and in effect, its corresponding graph as well, select the measure from the Existing Value(s) list, click the Delete button, and then click the Update button.
- To add a new graph, first, pick the Test that reports the measure for which a graph is to be generated.
- Next, select the Measure of interest.
- Provide a Display name for the measure. Then, click the Add button to add the measure to the Existing Values(s) list. Finally, click the Update button.
- This will add a new measure, summary, and trend graph for the chosen measure to the History tab page.
Note:
Only users with Admin or Supermonitor privileges can enable/disable the system, network, and application dashboards, or can customize the contents of such dashboards using the Dashboard Settings window. Therefore, whenever a user without Admin or Supermonitor privileges logs into the monitoring console, the button will not appear.