Foglight for Microsoft DOT NET 5.9.13 - Application Servers User Guide

Monitoring Application Servers

This Foglight for Application Servers User Guide provides instructions and conceptual information about how to monitor and display .NET and Java EE Technologies metrics, and JMX metrics from JMX-enabled systems.

In addition, this guide provides information about the Application Servers Administration and Monitor dashboards and views. This guide is intended for any user who is interested in monitoring .NET or Java EE systems, or JMX data with Foglight for Microsoft .NET, Foglight for Java EE Technologies, or Foglight for JMX. Guides that are common to these three products are called the Foglight for Application Servers guides.

The Application Servers Monitor dashboard provides a centralized location for monitoring your .NET, Java EE Technologies, and JMX systems, servers, deployed applications, requests, and methods. From this dashboard, you can view the health status of your monitored components, and investigate any alarms that occur.

NOTE: If you do not see the Application Servers Monitor dashboard listed in the navigation panel, inform your Foglight System Administrator. Your Administrator can add your user account to one of the following role groups: .NET Administrator, .NET Read-only, Java EE Administrator, or Java EE Read-only User, JMX Administrator, or JMX Read-only User. You must have one of these roles to be able to see the Application Servers Monitor dashboard.

NOTE: The tiles and views available on this dashboard depend on the products you have installed. For example, the Deployed Applications, Requests, and Methods tiles are only available when you have installed Foglight for Java EE Technologies or Foglight for Microsoft .NET.

The Application Servers Monitor dashboard displays services as defined by the default Application Servers service category. The Application Servers category contains all Java EE, JMX, and .NET services.

If you want to view only a specific subset of services (such as only All .NET Systems), you can select the service.

2	On the Application Servers Monitor dashboard, click the edit icon .

TIP: You may have to expand a service (click the ‘+’ sign) to locate the service you want.

You can select a different service to view at any time using the same procedure. You can also create your own services.

Using the Application Servers Monitor dashboard

The Application Servers Monitor dashboard organizes your .NET and Java EE Technologies monitoring data into views that are divided into five categories: Systems, Servers, Deployed Applications, Requests, and Methods. These categories are presented as tiles on the dashboard.

Click a tile to access the views for that category. For more information, see:

If you want to view only the components that have triggered alarms for that category, click the health status icon on the tile.

The health status icons act as a filter for the category, allowing you to focus on trouble spots within your system.

Some columns are not visible by default. You can use the customizer menu to show all available columns, or to reduce the number of columns shown if the information is not pertinent to your monitoring needs.

1	Click the Customizer icon at the top-right corner of any table.

Reviewing alarms

On the Application Servers Monitor dashboard, click the number next to Current Alarms: to open the Alarm Summary dialog box that lists the details of the current alarms.

Use these links to access more detailed information about the alarms affecting your monitored services.

For more information about managing alarms, see Viewing, Acknowledging, and Clearing Alarms in the Foglight User Help.

Managing services

In Foglight, a service is defined as a grouping of one or more monitored components, such as Java Service Pages (JSPs), servlets, and Enterprise Java Beans (EJBs). Services can be nested within other services, each with their own monitored components. Application Server (Java EE and .NET) services are organized by predefined types such as: all monitored domains, WebSphere cells, OracleAS cluster topologies, JBoss partitions, Tomcat servers, or web applications.