Page tree

Skip to end of metadata
Go to start of metadata

When you create or modify a dashboard, select and configure the Application Server Health dashlet to display key performance indicators for application servers that are monitored by App Visibility Manager. You can see a list of applications that use a selected server, and see graphs of the following metrics over time:

  • Number of hits per second
  • Percentage of transactions with latency violations and errors
  • Percentage of server CPU usage
  • Amount of server memory usage

This topic presents the following information about this dashlet:

Understanding the dashlet data

The Application Server Health dashlet provides a general overview of an application server, displaying basic server metrics and a summary of application use on the server.

The following image is an example of the Application Server Health dashlet:

Application Server Health dashlet

A single instance of the dashlet displays four graphs of key performance indicators over time, as follows:

Hits per second, based on the total number of hits on the server

Percentage of CPU usage on the server:

  • (Java) Average percentage of CPU used by the JVM process
  • (.NET) Average percentage of CPU used by all traced ASP.NET worker processes

 Percentage of total transactions on the server with latency violations and errors

 Memory usage, in megabytes, of the server:

  • (Java) Average consumed memory, consisting of heap and non-heap memory
  • (.NET) Average values of virtual and private memory that are used by all traced ASP.NET worker processes

The selected time filter in the image is set to the last two days, which is determined by the dashboard Time Period setting. For more information about setting the time for the dashboard, see Adding and modifying dashboards .

Example

As an IT operator, you see that as the number of hits per second increases, CPU usage and memory usage increases more quickly. The trends are expected, and you would monitor these, and other correlations, to help locate areas of degradation.

The upper part of the dashlet displays the following general information about the application server:

  • Name of the server followed by the server type in parentheses
  • List of applications that use the server
  • Current severity of the events on the server (OK, warning, or critical)
  • (Java) Server uptime that is, the amount of time since the server was last restarted

If the application server is currently offline, the severity and uptime are not displayed, and the following indicators are displayed instead:

  • Offline, for servers monitored by the agent for Java
  • N/A, for servers monitored by the agent for .NET

You can examine data in the dashlet by performing the following tasks:

Drill down to applications that use the server

The applications that use the selected application server are displayed in the upper part of the dashlet, under the server name. Click an application name to see the application server selected in the Application View.

If no applications use the server, or if you do not have permission to access applications that use the server, N/A (not applicable) is displayed.

Notes

Only the applications for which you have permissions are displayed, yet the graphs display the total values for all applications that use the server—that is, you can see the number of hits per second, percentage of latency violations, and percentage of errors.

Even if you do not have permission to view any of the applications that use the server, the dashlet graphs still represent the total use on the application server.

View tooltips over data points in the graph

Hover over a point in a graph to see the value and time.

View information in the graph legend

Hover over a point in a graph and the graph's legend displays values for all the items.

Click an item in the graph legend to hide or show data on the graph. In this way, you can hide data that is not relevant to you or you can separate overlapping data points, which might be useful on the graph showing the percentage of latency violations and errors. The data points are displayed again the next time that the page or dashlet is refreshed.

Zoom in to a specific time frame

Drag horizontally over a graph to zoom in to a specific time frame. To return to the standard view, click  Show all in the upper-right side of the graph.

Dashlet requirements

The Application Server Health dashlet requires application servers on which an App Visibility agent for Java or .NET is installed.

When you configure the dashlet, you select an application server. The dashlet is not affected by a dashboard's application filter.

Configuring the dashlet

You can configure this dashlet when you add or edit a dashboard .

  1. Click Add Dashlet and select the Application Server Health dashlet.
  2. Click the Configure Dashlet icon.

  3. (Optional) Enter a descriptive title for the dashlet.
  4. To choose an application server, click Select to open a list of servers monitored by App Visibility agents for Java or .NET.
    After you configure the dashlet for the first time, click Change to change the selected application server.
  5. Select the height of the dashlet row: 3X or 4X.
    The value of X is approximately 100 pixels. The default height is 4X.

Related topics

Application metrics and problems

Adding and modifying dashboards

Dashlet library

Adding and editing components