Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Foglight for Microsoft DOT NET 5.9.13 - Application Servers User Guide

Monitoring Application Servers Monitoring Systems Monitoring Servers Monitoring Deployed Applications Monitoring Requests Managing Traces Using Object Tracking to Locate Memory Leaks Monitoring Methods Application Servers Monitor Views
JVM view Method Groups view Request Types view Entity EJBs view Message Driven EJBs view Stateful Session EJBs view Stateless Session EJBs view Deployed Applications view JSPs/Servlets components view Resource Adapters components view Web Applications components view Web Services components view .NET views JBoss Services views Oracle Services views Tomcat Services views WebLogic Services views WebSphere Services views JMX Administration dashboard JMX Explorer dashboard
Appendix: Regular Expressions

Investigating system component health

The health of a system depends on the health of its servers, applications, and components (where applicable). Using the System view of the Application Servers Monitor dashboard, you can drill down to investigate the health of an individual system component.

For more information about the rules that generate alarms for the JVM, review the rules on the Foglight Rule Management dashboard (Dashboards > Administration > Rules & Notifications > Rules > search for “JVM”).

The JVM is just one example of a component for which there are drill-down views. Other examples include Web Applications, Web Services, EJBs, Requests, Services, Application Pools, and Sites. In all cases, you can access these drilldown views by clicking the name of an object or component in a health status pop-up, as described in the previous example.

For more information about individual views, see Application Servers Monitor Views .

 

Monitoring Servers

Use the Servers tile of the Application Servers Monitor dashboard to monitor specific application servers. From this view, you can investigate individual application servers in your internal and remote infrastructure and review the invoked operations that these application servers use.

To learn more about the supported application servers, see one of the following guides:

From this view, you can perform the following actions:

1
On the navigation panel, under Dashboards, click Application Servers > Monitor. The Application Servers Monitor dashboard opens.
2
Click the Servers tile.

The Servers table lists all the application servers running in your environment. Use this table to review the health and version of any monitored application server, as well as the availability (up time as a percentage), and any outages. Select an application server in this table to display detailed information in the Server Details view on the right.

This view provides details about the server that you select in the Server table, including: Request Types, Method Groups, health of the JVM, Applications, any collected MBean components, EJBs, and Services.

Each monitored component in the server details view has a health status icon, and each component name is a link. To view the health summary for the component, click the status icon. For more information, see Reviewing the health of your systems.

To view more details about a component, click the name link. A pop-up or drilldown view opens, providing more information. For example, click JVM to open the Java Virtual Machine (JVM) view.

The Quick View option provides condensed charts that show the general state of a selected system. These charts answer questions such as: What are the slowest three requests on server ABC, or what thread pools have the most waiters? The Quick View Selection menu differs for application server type. The following table outlines the charts available for each application server.

Sites — Current Connections

Period average of current connections to the web site.

Web Applications — Request Rate

The number of requests run per second by the application.

Site — Request Throughput

The rate, in seconds, at which all HTTP requests have been received.

Web Application — Timed Out Requests

Count of web application requests that timed out.

Application Pool — Exception Count

Count of exceptions that occurred in the application pool.

Application Pool — % Processor Time

Percentage of processor time the application pool uses, as a period average.

Executable/Service — Exception Count

Count of exceptions that occurred in all standalone executables and Windows services applications monitored by the server.

Executable/Service — % Processor Time

Current processor time used by all monitored executable and Windows services applications.

Slowest Response Times

Request with longest response times on average.

Longest Wait Times

Queues with the longest wait times on average.

Most Active Topics

Topics with largest incoming message rate on average.

Highest Pool Usage %

EJB pools with highest usage percentage on average.

Slowest Service Times

JSPs/Servlets with the lowest service times on average.

Slowest Response Times

Requests with longest response times on average.

Longest Queues

Thread pools with largest number of requests in their thread pools on average.

Longest Total Wait Times

JSBC connection pools with the longest total time all requests spent waiting for a connection.

Slowest Service Times

JSPs/Servlets with the longest request times on average.

Requests — Slowest Response Times (ms)

Slowest response time for each request traced.

JVM — Heap Usage

Capacity and Used memory.

JSP/Servlets — Error Count (c)

JSP/Servlets with the highest number of errors.

JSP/Servlets — Service Time (ms)

JSP/Servlets using the highest time on average.

Thread Pools — Highest Pool Usage

Thread pools which are being used most of the time.

Requests — Slowest Response Times (ms)

Request with the longest response time on average.

JVM — Heap Usage

Capacity and Used memory.

JVM — Garbage Collector

Garbage collector rate and overhead.

Work Managers — Most Waiters

Work managers with the highest number of waiters in their queues on average.

EJBs — Highest Cache Miss %

EJBs with the highest cache miss percentage on average.

EJBs — Highest Pool Miss %

EJBs with the highest pool miss percentage on average.

JSPs/Servlets — Most Invocations

JSPs/Servlets with the most invocations.

Execute Queues — Most Pending Requests

Run queues with the highest pending request count in their queues on average.

Local JMS Servers — Most Pending Messages

JMS servers with the highest pending message count on average.

JDBC Data Source — Most Connection Waiters

JDBC data sources with the highest number of threads waiting for a connection on average.

Requests — Slowest Response Time (ms)

Requests with longest response time on average.

JVM — Heap Usage

Capacity and Used memory.

Thread Pools — Highest Pool Usage %

Thread pools with highest utilization on average.

JDBC Data Source — Most Threads Waiting

JDBC data sources with highest number of threads waiting for a collection.

JSPs/Servlets — Most Popular

JSPs/Servlets accessed (requested) the most.

JCA Pools — Most Waiters

JCA Pools with highest number of threads waiting on average.

EJBs — Lowest Hit Ratio %

EJB pools with lowest hit ratios.

1
On the navigation panel, under Dashboards, click Application Servers > Monitor. The Application Servers Monitor dashboard opens.
2
Click the Servers tile.
3
Click Quick View, or the edit icon beside the text.
5
Click OK to close the dialog box. The Quick View refreshes.

Viewing JVM data for systems or servers

You can access Java Virtual Machine (JVM) details for an MBean Server from either the Systems view or the Servers view of the Application Servers Monitor dashboard.

1
On the navigation panel, under Dashboards, click Application Servers > Monitor. The Application Servers Monitor dashboard opens.
2
Click the Systems tile.
1
On the navigation panel, under Dashboards, click Application Servers > Monitor. The Application Servers Monitor dashboard opens.
2
Click the Servers tile.
Click JVM in the server details view. The JVM view opens.
Click Quick View, located just below the server details view, and select JVM — Heap Usage from the dialog box that opens. Click OK. The JVM Heap Usage chart appears in the Quick View area.

The top portion of this view lists the System, Server, and Health information. Click any status icon to review the health of that component. For more information about the rules that determine the Java Virtual Machine (JVM) health status, review the rules on the Foglight Rule Management dashboard (Dashboards > Administration > Rules & Notifications > Rule Management > search for “JVM”).

The charts in the middle section give you a quick view of the JVM Heap Used and Committed, Garbage Collection (GC), and Process Metrics, including:

In addition to viewing the heap usage of your JVM, it is important to understand how frequently garbage collection is run (GC Rate) and the percentage of time your JVM is spending on garbage collection (GC Overhead).

To see more details about the JVM, click one of the tabs in the JVM view below the charts. For more information, see JVM view.

Monitoring Deployed Applications

On the Application Servers Monitor dashboard, the Deployed Applications tile lists all the deployed applications running in a monitored environment (domain, cell, cluster topology, server group, or partition) and the related components, such as Application Pool, EJBs, Web Applications, and the Web Services health status. From here you can drill down to explore the components in further detail.

Use this view to investigate the deployed applications running in your infrastructure. Select an application in the table to display a list of the various types of components that are running in a specific application and their deployment details.

From this view, you can perform the following actions:

Collect Traces (from the Action panel > General)
1
On the navigation panel, under Dashboards, click Application Servers > Monitor. The Application Servers Monitor dashboard opens.
2
Click the Deployed Applications tile.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation