지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight for Java EE Technologies 5.9.7.5 - Application Servers User Guide

Monitoring Application Servers Monitoring Systems Monitoring Servers Monitoring Applications Monitoring Requests Managing Traces Using Object Tracking to Locate a Memory Leak 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

Agent Instance Overrides view

Purpose
Use this view to specify which MBean instances you want to collect for a selected agent. By default all exposed MBean objects are collected. By setting overrides you are able to reduce the amount of unnecessary data you are collecting from your monitored hosts.
Use this view to do the following:
•
Specify collection overrides to collect all available instances, or reduce the data collected by specifying only some available instances
•
Use an object name query to specify which instances to include or exclude in your data collection
How to get here
On the Application Servers ADministration dashboard, click the name of a JMX agent in the Monitoring Agents table. In the list that opens, select Agent Overrides.
Description of the View
 
Table 72. Available MBean Types table
Data Displayed
•
Type. A list of MBean type instances available for collection.
•
Agent Override. The state of the overrides.
•
Server Model. The default state of the instances being collected, as defined by the server model.
Where to go next
Drill down on:
The value in the Type column. The Monitored Instance Overrides dialog box opens.

Agents Using Server Model view

Purpose
Use this view to identify which agents are using a particular server model without leaving the Server Model tab of the JMX Administration dashboard.
Use this view to do the following:
•
specify collection overrides to collect all available instances, or reduce the data collected by specifying only some available instances.
•
use an object name query to specify which instances to include or exclude in your data collection.
How to get here
To access this view:
1
Open the JMX Administration dashboard.
2
If the Used by column is not included in the Server Models table, click the customizer icon (located at the top right corner of the table), and use the menu to add the column to the table.
3
Click an entry in the Used by column for a server model that at least one agent is using.
Description of the view
Table 73. Agents Using Server Model table
Data Displayed
•
Name. The name of the agent.

Server Model Editor dashboard

Purpose
Use this dashboard to review which MBean types are configured for collection. From here you can select and configure the attributes you want to collect, set the exposed relationships, customize the display name for the MBean type (so that the MBean information listed in the Java EE Monitor dashboard is more meaningful for the user,) and edit the type configuration.
How to get here
On the JMX Administration dashboard, click an entry in the Name column of the Server Models table. In the list that opens, select Edit.
Description of the view
 
Table 74. Configured MBean Types table
Data Displayed
•
Name. The name of the MBean root type.
•
Instance Availability. Indicates the availability for monitoring of MBean instances of the root type. For example, All by Root Query indicates that all instances are available for monitoring using a root query.
•
Monitored Instances. Indicates the MBean instances that are monitored by default.
•
Collected Attributes. The number of attributes of the MBean instance that are being collected, as a fraction of all available attributes (for example 2/25).
•
Exposed Relationships. The number of relationships that have been exposed for the selected MBean instance.
•
Display Name. The display name of the MBean instance, if different from the default name.
Where to go next
Drill down on:
•
Add Root Type. Starts the wizard for adding root types.
•
Update Type Definitions. Updates the list of type definitions, if at least one agent is connected to the MBean server.
•
Name. Opens a list of options for managing configurations.
•
Monitored Instances. Opens a dialog box that allows you to define instances to monitor.
•
Collected Attributes. Opens a dialog box that allows you to select and configure attributes for collection.
•
Exposed Relationships. Opens a dialog box that allows you to expose MBean relationships.
•
Display Name. Opens a dialog box that allows you to change the display name for an MBean.
 
Table 75. Agents and Monitored Instance Overrides table
Data Displayed
•
Name. The name of the agent.
•
Overrides. The number of MBean instance overrides for the agent, displayed as a fraction of total MBean instances available (for example, 02/25).
Where to go next
Drill down on:
•
Overrides. Opens the Instance Overrides dialog box for the selected MBean type and agent.

JMX Explorer dashboard

Purpose
Use the JMX Explorer dashboard to get a quick overview of how many MBeans are currently being monitored. From this view you can select an MBean to view its properties.
How to get here
On the navigation panel, under Dashboards, click Application Servers > JMX > Explorer.
Embedded views
This dashboard is composed of the following embedded views:
•
Available MBeans
•
MBean Summary view
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택