vFabric Hyperic Resource Configuration and Metrics...2008/06/05 · SpringSource tc Runtime 7.0...

Page of 1 824

vFabric Hyperic ResourceConfiguration and Metrics

VMware vFabric Hyperic 5.0

This document supports the version of each product listed andsupports all subsequent versions until the document is replacedby a new edition. To check for more recent editions of thisdocument, see .http://www.vmware.com/support/pubs

EN-000959-00

http://www.vmware.com/support/pubs

Page of 2 824

You can find the most up-to-date technical documentation on the VMware Web site at:

http://www.vmware.com/support/

The VMware Web site also provides the latest product updates.

If you have comments about this documentation, submit your feedback to:

[email protected]

Copyright © 2013 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright andintellectual property laws. VMware products are covered by one or more patents listed at

.http://www.vmware.com/go/patents

VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All othermarks and names mentioned herein may be trademarks of their respective companies.

VMware, Inc.3401 Hillview Ave.Palo Alto, CA 94304www.vmware.com

http://www.vmware.com/support/mailto://[email protected]://www.vmware.com/go/patents

Page of 3 824

Table of Contents

1 About vFabric Hyperic Resource Configuration and Metrics 9Intended Audience 9

2 GemFire 10GemFire Plugin Overview 10

Resource Types and Management Functions 12

Configuration Instructions 17

Metric Documentation 18

GemFire Events 20

Hyperic GemFire View 21

3 Java Applications 25Auto-Discovery of Custom MBeans 25

Prerequisites and Supported Environments 25

Step 1 - Set Up Resources to Export ModelMBeans 27

Step 2 - Verify Model MBean Export to MBeanServer 27

Step 3 - Verify Service Application Auto-Discovery 27

Step 4 - Configure App Services as an Application in HQ 28

Model MBean Naming and Descriptor Data 28

4 JBoss 33Monitoring JBoss 33

JBoss Configuration Tracking 33

JBoss Metrics 34

JBoss 7 server 36

JBoss Managed 7 server 41

JBoss Host Controller 7 server 46

JBoss 6.0 server 47

JBoss 5.1 server 57

JBoss 5.0 server 66

JBoss 4.3 server 74

JBoss 4.2 server 85

JBoss 4.0 server 94

JBoss 3.2 server 102

Page of 4 824

5 Local Platform Services 110When to Manually Create a Platform Service 110

Create a Platform Service 110

Configuration Instructions for Platform Services 111

FileServer Directory Service 114

FileServer Directory Tree Service 115

FileServer File Service 116

FileServer Mount Service 118

Multiprocess Service 119

Process Service 121

Script Service 123

CPU Service 125

NetworkServer Interface Service 126

Windows Service Service 127

6 Microsoft Exchange 130Microsoft Exchange Overview 130



Exchange Metrics 132

Exchange 2010 server 133

Exchange Transport 2010 server 149

Exchange 2007 server 153

Exchange Transport 2007 server 169

7 Microsoft SQL Server 174Microsoft SQL Server Plugin Overview 174



SQL Server Metrics 176

MsSQL 2012 server 176

MsSQL 2008 R2 server 182




8 Nagios 199Nagios Resources and the Hyperic Inventory Model 199

Management Functions 200

Configure Nagios Monitoring 201

View Nagios Resources and Metrics in Hyperic 202

Page of 5 824

9 NetApp Filer 206NetApp Filer Plugin Overview 206


Understand NetApp Plugin Management Functions and Metrics 210

Solving Problems 220

NetApp Filer platform metrics 221

10 Network Device 230Monitoring a Network Device 230



Solving Problems 242

11 Network Platform Services 244Hyperic Network Service Monitoring Capabilities 244

Configuration Requirements and Options for Monitoring Network Services 245

Metrics for Network Services 245

Classes for Monitoring a Network Service 246

Services Hyperic Can Monitor Over the Network 246

DHCP Platform Service 246

DNS Platform Service 249

FTP Platform Service 252

HTTP Platform Service 256

IMAP Platform Service 261

InetAddress Ping Platform Service 264

LDAP Platform Service 267

NTP Platform Service 271

POP3 Platform Service 273

RPC Platform Service 277

SMTP Platform Service 280

SNMP Platform Service 283

SSH Platform Service 286

TCP Socket Platform Service 289

12 PostgreSQL 293PostgreSQL Plugin Overview 293



PostgreSQL Metrics 298

vPostgres 9.x server 298

PostgreSQL 9.x server 302

HQ PostgreSQL 9.x server 307

PostgreSQL 8.x server 311

PostgreSQL 7.4 server 315

Page of 6 824

13 RabbitMQ 320RabbitMQ Plugin Overview 320



RabbitMQ server 329

14 Spring Application server 333

15 Spring Insight 334Spring Insight Plugin Overview 334

Spring Insight Resources and the Hyperic Inventory Model 335

Installation Environment 335



16 tc Server 341Configure a tc Server Instance 342

Manage tc Server Applications 349

tc Runtime JDBC Reference 360

Metrics 369

SpringSource tc Runtime 6.0 server 370

SpringSource tc Runtime 7.0 server 378

17 vFabric Web Server 388vFabric Web Server Plugin Overview 388



vFabric Hyperic Web Server Metrics 389

vFabric Web Server 5.1 server 390

vFabric Web Server 5.2 server 392

18 vSphere 395vSphere Plugin Overview 395

vSphere Components in the Hyperic User Interface 400



Sun JVM 427

Events 429

Page of 7 824

19 WebLogic Server 562Introduction 562

Configuration Overview 562

Configure WebLogic Server Monitoring 563

Troubleshoot WebLogic Server Auto-Discovery Problems 567

Configuration Files Tracked by Default 571

Metrics 571

Weblogic 6.1 server 572









Weblogic Admin 6.1 server 681








Weblogic NodeManager 6.1 server 785









20 WebSphere MQ 789Configuration Requirements 789

Metrics 790

21 WebSphere 800WebSphere Plugin Overview 800




WebSphere 6.0 server 804



WebSphere Admin 6.0 server 820



Page of 8 824

The pages below document selected VMware® vFabric™ Hyperic® product plugins.

If the plugin you are looking for is not listed below

For Hyperic plugins not listed below, see http://support.hyperic.com/display/hyperforge/Home, the Hyperic Community

site.

About vFabric Hyperic Resource Configuration and Metrics (see page 9)

GemFire (see page 10)

Java Applications (see page 25)

JBoss (see page 33)

Local Platform Services (see page 110)

Microsoft Exchange (see page 130)

Microsoft SQL Server (see page 174)

Nagios (see page 199)

NetApp Filer (see page 206)

Network Device (see page 230)

Network Platform Services (see page 244)

PostgreSQL (see page 293)

RabbitMQ (see page 320)

Spring Application server (see page 333)

Spring Insight (see page 334)

tc Server (see page 341)

vFabric Web Server (see page 388)

vSphere (see page 395)

WebLogic Server (see page 562)

WebSphere MQ (see page 789)

WebSphere (see page 800)

Page of 9 824

About vFabric Hyperic Resource

Configuration and Metrics

documents the configuration requirements and metrics available forvFabric Hyperic Resource Configuration and Metrics

selected VMware vFabric™ Hyperic® and Hyperic HQ product plug-ins. This guide supplements vFabric Hyperic

Administration.

Intended Audience

is intended for Hyperic administrators who configure resources forvFabric Hyperic Resource Configuration and Metrics

monitoring.

1

Page of 10 824

GemFire

Topics marked with * relate to features available only in vFabric Hyperic.

GemFire Plugin Overview (see page 10)

Supported Versions (see page 11)

GemFire Resources and the Hyperic Inventory Model (see page 11)

Configuration Overview (see page 12)

Resource Types and Management Functions (see page 12)

Management Functions for GemFire Distributed System (see page 13)

Management Functions for JMX Agent (see page 13)

Management Functions for Cache Server 6.5 (see page 13)

Management Functions for Cache Server 6.5 Region (see page 14)

Management Functions for Gateway Hub 6.5 (see page 14)

Management Functions for Gateway Hub 6.5 Gateway (see page 15)

Management Functions for Gateway Hub 6.5 Region (see page 15)

Management Functions for Application Peer 6.5 (see page 16)

Management Functions for Application Peer 6.5 Region (see page 16)

Configuration Instructions (see page 17)

Step 1: Enable GemFire Member Discovery and Monitoring (see page 17)

Step 2: Configure Hyperic Agent for the DS (see page 17)

Step 3: Configure a Platform for the DS (see page 17)

Step 4: Set Event Tracking Options (see page 18)

Step 5: Tailor Plugin Monitoring Defaults (see page 18)

Step 6: Configure Alert Definitions (see page 18)

Metric Documentation (see page 18)

GemFire Distributed System Metrics (see page 18)

Member Metrics (see page 19)

Region Metrics (see page 20)

Gateway Hub 6.5 Gateway Metrics (see page 20)

GemFire Events (see page 20)

Hyperic GemFire View (see page 21)

GemFire View for a DS (see page 21)

GemFire View for a Cache Server or Application Peer (see page 23)

GemFire View for a Gateway Hub (see page 24)

This page documents Hyperic's GemFire plugin.

2

Page of 11 824

GemFire Plugin Overview

Hyperic's GemFire plugin manages a GemFire Distributed System (DS) and the servers and services it comprises. The

indented list of resource types below illustrates the hierarchical relationships among that managed components of a

GemFire DS. Each resource type is described below in GemFire Resources and the Hyperic Inventory Model (see page 11

.)

GemFire Distributed System

JMX Agent

Cache Server 6.5

Cache Server 6.5 Region

Application Peer 6.5

Application Peer 6.5 Region

Gateway Hub 6.5

Gateway Hub 6.5 Gateway

Gateway Hub 6.5 Region

Supported Versions

The GemFire plugin supports GemFire v6.5

GemFire Resources and the Hyperic Inventory Model

The table below has a brief description of each GemFire resource type; the right column indicates the inventory level for a

type in the Hyperic inventory model.

GemFire

Resource

Hierarchy

Description Inventory

Type

GemFire

Distributed

System

(DS)

GemFire is a distributed caching system. A GemFire (DS) is a logical entityDistributed System

--- a set of servers that are configured to communicate with one another. The servers in a DS

are referred to as or . Member types (defined in the rows below) include:members nodes

JMX Agent

Gateway Hub 6.5

Cache Server 6.5


platform

JMX Agent A GemFire is an administrative member of a DS through which the Hyperic AgentJMX Agent

obtains GemFire resource and metric data. The JMX Agent returns ModelMBeans attributes

that correspond to inventory properties and metric values for members of the DS.

server

Gateway

Hub 6.5

A is present in a DS that is part of a multi-DS deployment. The Gateway Hub forGateway Hub

a DS:

Creates and manages Gateways for communicating with remote DSs,

Receives gateway events from other DSs, and distributes the events to one or all local

gateways, in accordance with its distribution policy.

Hosts a GemFire cache.

server

Page of 12 824

Gateway

Hub 6.5

Gateway

A manages a queue of events (where an event is an operation that affects a specificGateway

region) to be propagated to a particular remote DS.

service

Cache

Server 6.5

A is a server for cached objects. (As opposed to a GemFire Application Peer,Cache Server

which is a GemFire cache within an application).

server

Application

Peer 6.5

An is an application process running a GemFire cache.Application Peer server

regions In GemFire, a region is a set of cached objects that are managed in accordance with the same

policies. For example, rules for expiration, data policy, scope, the directories to which region

data is written, the Gateway Hub to which region events are distributed, and so on.

A region can have subregions, which in turn can have their own subregions. Regions provide a

hierarchical namespace for sets of objects in a cache. A region can exist in any non-admin

member of the DS. The name of a region in Hyperic indicates the resource type of its parent in

the managed resource hierarchy:




service

For more information about the managed resource hierarchy, see Resources, Resource Types and Inventory Types in Note:

.vFabric Hyperic Overview

Configuration Overview

The GemFire plugin uses the GemFire JMX Agent to obtain inventory properties and metrics for the GemFire components

in a GemFire Distributed System (DS). You configure a Hyperic Agent to communicate with the DS's JMX Agent. The

Hyperic Agent can run on the same platform as the JMX Agent, or on another platform.

The key requirements for successfully managing GemFire components with Hyperic are:

The Hyperic Agent must be able to connect to the JMX Agent. If the Hyperic Agent is on a different platform than the

JMX Agent for the DS, you must ensure that the Hyperic Agent can connect to the JMX Agent's RMI service.

Each GemFire member's property (in its file) must bestatistic-sampling-enabled gemfire.properties

set to . The default value for the property is .true false

Page of 13 824

Resource Types and Management Functions

Management Functions for GemFire Distributed System

Management

Function

Description Classes

Auto-discovery The GemFire plugin does not automatically discover the platform

resource — you explicitly create the resource, and configure it to

connect to the JMX Agent for the DS, as described in the

.Configuration Instructions (see page 17)

com.vmware.springsource.hyperic.

plugin.gemfire.detectors.

GemfirePlatformDetector

Metric

Collection

The class obtains data about DSGemfireCollector

membership and presents it as metrics for the platform resource.

See .GemFire Distributed System Metrics (see page 18)


plugin.gemfire.collectors.

GemfireCollector

Event Tracking If event tracking is configured for the DS, the AlertsPlugin

class logs an event for each of the GemFire alert types listed in

.GemFire Events (see page 20)


plugin.gemfire.AlertsPlugin

Live Data The class provides a live data user interfaceGemFireLiveData

for viewing member metrics in real-time. (As opposed to the

tab for a GemFire component, which presents metricsMonitor

that have been saved to the Hyperic database.) See Hyperic

.GemFire View (see page 21)


plugin.gemfire.GemFireLiveData

Management Functions for JMX Agent

Management

Function

Description Classes

Auto-discovery The JMX Agent for a DS is discovered when the plugin connects

to the JMX connection configured for the DS platform.



JMXAgentDetector

Metric

Collection

The class reports the Availability of aJMXAgentCollector

JMX Agent based on its ability to connect to it and query for

member information.

com.vmware.springsource.hyperic

.plugin.gemfire.collectors.

JMXAgentCollector

Management Functions for Cache Server 6.5

Management

Function

Description Classes

Page of 14 824

Auto-Discovery A Cache Server is discovered via JMX Agent for the DS. The

class obtains inventory propertiesCacheServerDetector

from the ModelMBean for aMemberInfoWithStatsMBean

Cache Server. This list indicates the MBean attribute that supplies

each property:

ID - The gemfire.member.id.string

Type - gemfire.member.type.string

Peer Host - gemfire.member.host.string

Peer Port - gemfire.member.port.string



CacheServerDetector

Metric

Collection

The plugin obtains metrics for Cache Server from the GemFire

ModelMBean for the serverMemberInfoWithStatsMBean

via the JMX Agent for the DS. Each metric corresponds to an

attribute of the MBean.

For more information, see .Member Metrics (see page 19)



MemberCollector

Management Functions for Cache Server 6.5 Region

Management

Function

Description Classes

Auto-Discovery The class obtains inventoryCacheServerDetector

properties from the MemberInfoWithStatsMBean

;ModelMBean for a Region in a Cache Server. This list indicates

the MBean attribute that supplies each property:

Name - gemfire.region.name.string

Path - gemfire.region.path.string

Scope - gemfire.region.scope.string

Data Policy - gemfire.region.datapolicy.string

Interest Policy - gemfire.region.interestpolicy.string

Disk Attributes - gemfire.region.distattrs.string



CacheServerDetector

Metric

Collection

The class obtains metrics for a Region in aRegionCollector

Cache Server from the GemFire

ModelMBean for the server.MemberInfoWithStatsMBean

Each metric corresponds to an attribute of the MBean. See Region

.Metrics (see page 20)



RegionCollector

Management Functions for Gateway Hub 6.5

Management

Function

Description Classes

Page of 15 824

Auto-Discovery The GemFire plugin discovers members of a DS via the JMX

Agent for the DS. The class obtainsGatewayHubDetector

inventory properties from the MemberInfoWithStatsMBean

ModelMBean for a Gateway Hub. This list indicates the MBean

attribute that supplies each property:







GatewayHubDetector

Metric

Collection

The obtains metrics for a GatewayGatewayHubCollector

Hub from the GemFire {{MemberInfoWithStatsMBean}

ModelMBean for the server. Each metric corresponds to an

attribute of the MBean. See .Member Metrics (see page 19)



GatewayHubCollector

Management Functions for Gateway Hub 6.5 Gateway

Management

Function

Description Classes

Auto-Discovery The class obtains inventory propertiesGatewayHubDetector

for a Gateway from the GemFire

ModelMBean for theMemberInfoWithStatsMBean

Gateway Hub server. Each metric corresponds to an attribute of

the MBean.



GatewayHubDetector

Metric

Collection

The class obtains metrics for a GatewayGatewayCollector

from the GemFire MemberInfoWithStatsMBean

ModelMBean for the Gateway Hub server. Each metric

corresponds to an attribute of the MBean.

For more information, see See Gateway Hub 6.5 Gateway Metrics

.(see page 20)



GatewayCollector

Management Functions for Gateway Hub 6.5 Region

Management

Function

Description Classes

Page of 16 824

Auto-Discovery The class obtains inventory propertiesGatewayHubDetector

for a region in the Gateway Hub from the


Gateway Hub. This list indicates the MBean attribute that supplies

each property:

ID - gemfire.member.id









GatewayHubDetector

Metric

Collection

The class obtains metrics for a region in aRegionCollector

Gateway Hub from the GemFire


Gateway Hub. See .Region Metrics (see page 20)



RegionCollector

Management Functions for Application Peer 6.5

Management

Function

Description Classes

Auto-Discovery The GemFire plugin discovers members of a DS via the JMX

Agent for the DS. The classApplicationServerDetector

obtains inventory properties from the

ModelMBean for anMemberInfoWithStatsMBean

Application Peer. This list indicates the MBean attribute that

supplies each property:







ApplicationServerDetector

Metric

Collection

The plugin class obtains metrics for anMemberCollector

Application Peer from the GemFire

ModelMBean for the server.MemberInfoWithStatsMBean

Each metric corresponds to an attribute of the MBean.See

Member Metrics (see page 19)



MemberCollector

Management Functions for Application Peer 6.5 Region

Management

Function

Description Classes

Page of 17 824

1.

2.

1.

2.

Auto-Discovery The class obtainsApplicationServer Detector

inventory properties for a region in the Application Peer from the


Application Peer. This list indicates the MBean attribute that

supplies each property:









ApplicationServerDetector

Metric

Collection

The class obtains metrics for a region in aRegionCollector

Application from the GemFire


Application Peer. Each metric corresponds to an attribute of the

MBean. See .Region Metrics (see page 20)



RegionCollector

Configuration Instructions

Perform these steps for each DS to be managed.

Step 1: Enable GemFire Member Discovery and Monitoring

Follow these steps to ensure that the GemFire plugin can discover and monitor GemFire components:

If you plan to run the Hyperic Agent on the same platform as the JMX Agent for the DS, skip to Step 2. If you plan to

run the Hyperic Agent on a platform than the JMX Agent for the DS, you must ensure that the Hyperic Agentdifferent

can connect to the JMX Agent's RMI service — you can do this by specifying the JMX Agent's rmi-bind-address

when you start it:

./agent start rmi-bind-address=IP_Address -dir/AgentHome

Enable statistics sampling for each GemFire member in the DS — by default, statistics sampling is not enabled. To

enable it, edit each member's file to set the propertygemfire.properties statistic-sampling-enabled

to .true

Step 2: Configure Hyperic Agent for the DS

If you have not already done so, either:

install a Hyperic Agent to monitor the DS, either on the same platform as the JMX Agent, or on another platform (see

Install an Agent-Only Package in for instructions), orGetting Started with vFabric Hyperic

Select an existing Hyperic Agent on a remote platform to monitor the DS.

Step 3: Configure a Platform for the DS

These instructions assume the Hyperic Agent that will monitor the DS is up and running.

.Resources > Browse

Click on the menu.New Platform Tools

Page of 18 824

3.

a.

b.

i.

ii.

iii.

iv.

v.

c.

1.

2.

3.

On the page:New Platform

In the "General Properties" section, enter a meaningful name for the DS, and as desired, a description and its

location.

In the "General Properties" section,

Select from the pulldown.Gemfire Distributed System Platform Type

If the Hyperic Agent is on a different platform from the JMX Agent, select its address:port combination

from the pulldown.Agent Connection

Enter the FQDN of the platform where the JMX Agent runs.

Enter the IP Address of the platform where the JMX Agent runs.

Click .OK

In the "Configuration Properties" section of the page for the new platform:Inventory

— If the Hyperic Agent and the JMX Agent are on different platforms, edit the default JMXjmx.url

URL shown to include the IP address of the JMX Agent.

The default is:jmx.url

service:jmx:rmi:///jndi/rmi://localhost:1099/jmxconnector

In the correctly modified , is replaced by the hostname or address of thejmx.url localhost

JMX Agent, and the valid JMX connector listen port is specified:

service:jmx:rmi:///jndi/rmi://Host:Port/jmxconnector

— Enter the username for accessing the JMX Agent.jmx.username

— Enter the password for accessing the JMX Agent.jmx.password

Step 4: Set Event Tracking Options

To enable log tracking, click the box in the section of the Enable Log Tracking Monitoring Configuration Properties

page for the DS. Hyperic will log events of level "ERR" for the alert types listed in .GemFire Events (see page 20)

For information about Hyperic log tracking functionality and configuration options, and how to view log events, see Set Up

Log Tracking for a Resource.

Step 5: Tailor Plugin Monitoring Defaults

You can enable and disable metrics, select indicator metrics, and change the collection interval for a resource type on its

page. To navigate to a resource type's page:Monitoring Defaults Monitoring Defaults

Click the tab.Administration

Click .Monitoring Defaults

Scroll down to the resource type and click .Edit Metric Template

Step 6: Configure Alert Definitions

Create alert definitions as desired for your managed vSphere components.

Metric Documentation

The following sections define the metrics for each Gemfire resource type.

GemFire Distributed System Metrics

Name Alias Description Units Category Default

On

Default

Interval

Page of 19 824

Availability Availability The DS is considered available if the

Hyperic Agent can connect to the

JMX Agent for the DS.

percentage AVAILABILITY true 1 min

Cache

Servers

n_caches Number of Cache Servers in the DS. none UTILIZATION true 5 min

Applications

Peer

n_apps Number of Application Peers in the

DS.

none UTILIZATION true 5 min

Gateway

Hubs

n_gateways Number of Gateway Hubs in the DS. none UTILIZATION true 5 min

Member Metrics

The table below defines the metrics available for the server resources in a GemFire deployment.

Gateway Hub 6.5

Cache Server 6.5 Metrics


Name Alias Definition Units Category Default

On

Default

Interval

Availability Availability percentage AVAILABILITY true 5 min

Used Heap used_memory gemfire.

member.

stat.

usedmemory.

long

percentage UTILIZATION true 5 min

Used CPU used_cpu gemfire.

member.

stat.

maxmemory.long

percentage UTILIZATION true 5 min

Uptime uptime gemfire.

member.

uptime.l

ong

sec UTILIZATION true 30 min

Number of Clients nclients none UTILIZATION false 5 min

Gets stat.gets gemfire.

member.

stat.

gets.

int

none UTILIZATION false 10 min

Gets per Minute stat.gets1m none UTILIZATION false 10 min

Page of 20 824

GetTime stat.gettime gemfire.

member.

stat.

gettime.

long

sec UTILIZATION false 5 min

Puts stat.puts gemfire.

member.

stat.

puts.

int

none UTILIZATION false 10 min

Puts per Minute stat.puts1m none UTILIZATION false 10 min

PutTime stat.puttime gemfire.

member.

stat.

puttime.

long

sec UTILIZATION false 5 min

Region Metrics

The table below defines the metrics available for the region service resources in a GemFire deployment:




Name Alias Definition Units Category Default On Default Interval


Entry Count entry_count Number of regions;

gemfire.

region.

entrycount.

int


Gateway Hub 6.5 Gateway Metrics

Name Alias Definition Units Category Default On Default Interval


Queue size queuesize gemfire.

member.

gateway.

queuesize.

int


Page of 21 824

GemFire Events

Event Notification Type Notification Source Notification

Message

A new member has joined the

GemFire Enterprise DS.

gemfire.distributedsystem.member.joined ObjectName of the

member

String id of

the member

A member has left the GemFire

Enterprise DS

gemfire.distributedsystem.

member.left

ObjectName of the

member

String id of

the member

A member has crashed in the

GemFire Enterprise DS


member.crashed

ObjectName of the

member

String id of

the member

An alert raised from GemFire after

scraping the logs of members of

the GemFire Enterprise DS.


alert

String form of

ObjectName of the

AdminDistributedSystem

MBean

Message

containg the

alert details

in a fixed

format.

The agent has disconnected from

the GemFire Enterprise DS.


disconnect

String form of

ObjectName of the

AdminDistributedSystem

MBean

null

A cache is created on a member in

a GemFire Enterprise DS.


cache.created

ObjectName of the

member

A cache is closed on a member in

a GemFire Enterprise DS.


cache.closed

ObjectName of the

member

A region is created in a cache on a

member in a GemFire Enterprise

DS


cache.region.created

ObjectName of the

member

A region is removed from a cache

on a member in a GemFire

Enterprise DS.


cache.region.lost

ObjectName of the

member

Hyperic GemFire View

VMware vFabric™ Hyperic®'s GemFire plugin provides a live data user interface for viewing metrics in real-time. (As

opposed to the tab for a GemFire component, which presents metrics that have been saved to the HypericMonitor

database.)

Learn About GemFire Monitoring

See in .GemFire (see page 10) vFabric Hyperic Resource Configuration and Metrics

GemFire View for a DS

The HQ GemFire View for a Distributed System displays the following information.

Page of 22 824

Servers in the DS — The number of Cache Servers, Gateway Hubs and Application Peers in the DS.

Gateways in the DS — If the DS is part of a multi-site deployment, the number of Gateways in the DS's Gateway Hub.

Clients connected to the DS — The number of clients (Cache Servers, Gateways, or Application Peers) in other

Distributed Systems that are connected to the DS.

The table in the middle of the GemFire View for a DS displays inventory properties and last reported metric values for each

server (including Cache Servers, Gateway Hubs and Application Peers) the DS.

Page of 23 824

GemFire View for a Cache Server or Application Peer

The GemFire View for a Cache Server or Application Peer displays server and region inventory properties and metrics:

Server metrics — The single row table presents last reported metric values for the Cache Server or Application Peer.

Region metrics — The multi-row table presents inventory properties and the Entry Count metric for each region the

server contains.

Page of 24 824

GemFire View for a Gateway Hub

The HQ GemFire View for a Gateway Hub displays inventory data and live measurements for the Gateway Hub, the Hubs

and Regions it contains, and any clients connected to the Hub.

Page of 25 824

Java Applications


Auto-Discovery of Custom MBeans (see page 25)

Prerequisites and Supported Environments (see page 25)

Java Version (see page 25)

Supported Containers (see page 25)

Enable Discovery of a Stand-Alone Instrumented Java Application (see page 26)

MBeanServer (see page 26)

Create a MBeanServer in Tomcat (see page 26)

Create an MBeanServer for Stand-Alone Apps or Other Container (see page 26)

Enable ModelMBean Export in JBoss Containers (see page 26)

Step 1 - Set Up Resources to Export ModelMBeans (see page 27)

Step 2 - Verify Model MBean Export to MBeanServer (see page 27)

Step 3 - Verify Service Application Auto-Discovery (see page 27)

Solving Problems with Service Auto-Discovery (see page 27)

Step 4 - Configure App Services as an Application in HQ (see page 28)

Auto-Discovery of Custom MBeans

The HQ Agent can auto-discover and manage Java application services via Model MBeans that adhere to a specified

ObjectName naming convention and expose a specified set of service data. This enables you to monitor application services

along with the hosting application server and its internal services.

Prerequisites and Supported Environments

This section specifies requirements for HQ auto-discovery and management for Java application services.

Java Version

Auto-discovery of services exposed as ModelMBeans requires a version 1.5 or later JRE or JDK.

Supported Containers

The capability is supported for applications running in:

Tomcat v5.5 and later

WebLogic v9.1 and later

WebSphere v5.0 and later

JBoss v3.2 and later. See .Enable ModelMBean Export in JBoss Containers (see page 26)

SpringSource dm Server v1.0 and later

3

Page of 26 824

SpringSource tc Server v6.0 and later

Other containers that expose a JSR-160 connector. See Create an MBeanServer for Stand-Alone Apps or Other

.Container (see page 26)

Enable Discovery of a Stand-Alone Instrumented Java Application

To enable MBean discovery in a stand-alone Java Application, you must:

Instrument your code as specified in , or be using SpringModel MBean Naming and Descriptor Data (see page 28)

Framework instrumented jar files, and

Start the application with the system property. For example:spring.managed.application.name

java -Dcom.sun.management.jmxremote

-Dspring.managed.application.name="MyApplicationName" com.sample.MyApp

The application name will be set as the name of the discovered resource — in this example, .MyApplicationName

MBeanServer

The application servers listed in generally have an existing MBeanServer. If yourSupported Containers (see page 25)

container does not have an MBeanServer - as is the case with Tomcat if you haven't previously set it up - you must

configure one along with a JSR-160 connector. See the directions below.

Create a MBeanServer in Tomcat

If you wish to monitor applications running on Tomcat, make sure it has a MBeanServer. If it doesn't, you can create an

MBeanServer and associated

connector by setting the appropriate system properties at JVM startup.

You can add the system properties to the Tomcat start script, :$TOMCAT_HOME/bin/catalina.sh

[ $1!= "stop" ] && JAVA_OPTS="-Dcom.sun.management.jmxremote \

-Dcom.sun.management.jmxremote.port=6969 \

-Dcom.sun.management.jmxremote.ssl=false \

-Dcom.sun.management.jmxremote.authenticate=false $JAVA_OPTS"

export JAVA_OPTS

For more information, visit:

for information about setting system properties for your version of Tomcat. "http://tomcat.apache.org"

for information"http://download.oracle.com/javase/1.5.0/docs/api/javax/management/remote/package-summary.html"

about system properties that configure remote JMX access.

Create an MBeanServer for Stand-Alone Apps or Other Container

To create a MBeanServer for an application than runs stand-alone or a container other than those listed Supported

, set the JMX remote system properties in the application or container start script. These systemContainers (see page 25)

properties create a local MBeanServer and remote connector:

-Dcom.sun.management.jmxremote \

-Dcom.sun.management.jmxremote.port=6969 \

-Dcom.sun.management.jmxremote.ssl=false \

-Dcom.sun.management.jmxremote.authenticate=false \

http://tomcat.apache.orghttp://download.oracle.com/javase/1.5.0/docs/api/javax/management/remote/package-summary.html

Page of 27 824

Enable ModelMBean Export in JBoss Containers

There is a known issue with HQ discovery of services running in JBoss - when the JBoss interceptor publishes the MBeans

for the services, it does not export them as type "Model", preventing HQ from detecting them. You can work around this

issue by commenting out the following entry in

:JBOSS_HOME/server/default/deploy/jmx-invoker-service.xml

-->

Step 1 - Set Up Resources to Export ModelMBeans

Each Java class or service must instantiate Model MBeans that meet the requirements described in Model MBean Naming

.and Descriptor Data (see page 28)

There are multiple methods for creating Model MBeans. The process is not documented here. A variety of information is

available on the Sun site. Introductory material and examples are available in:

"Chapter 3 "Model MBeans" of the Java Dynamic Management Kit 5.0 Tutorial (

http://docs.sun.com/app/docs/doc/816-4178/6madjde4n?a=view)

"this blog (http://blogs.sun.com/jmxetc/entry/dynamicmbeans,_modelmbeans,_and_pojos...)

Redeploy your application after enabling export of Model MBeans.Note:

Applications with SpringSource Instrumented Jars

If your applications run with Spring instrumented JARs, they should automatically export Model MBeans with the

required name format and descriptors.

Applications using Spring 3.0 JMX Annotations

If your applications expose MBeans using the Spring 3.0 JMX annotations (@ManagedResource, @ManagedMetric,

@ManagedAttribute, @ManagedOperation), they should automatically be exported with the required descriptors.

Step 2 - Verify Model MBean Export to MBeanServer

To verify that your your application services have instantiated ModelMBeans, you can use a JMX client to browse the

MBeanServer.

Step 3 - Verify Service Application Auto-Discovery

The HQ Agent managing the server instance where your application runs should discover Model MBeans in the

MBeanServer that meet the requirements specified in .Model MBean Naming and Descriptor Data (see page 28)

The server instance that hosts the application will appear in the portlet on the Dashboard of the HQ userAuto-Discovery

interface. After you import the new or changed server instance to inventory, you can browse to the application services,

which will appear as children of the host server.

http://docs.sun.com/app/docs/doc/816-4178/6madjde4n?a=viewhttp://docs.sun.com/app/docs/doc/816-4178/6madjde4n?a=viewhttp://docs.sun.com/app/docs/doc/816-4178/6madjde4n?a=viewhttp://blogs.sun.com/jmxetc/entry/dynamicmbeans,_modelmbeans,_and_pojos...

Page of 28 824

1.

2.

3.

4.

5.

6.

Solving Problems with Service Auto-Discovery

If your application services were not discovered, verify that:

The hosting application server is enabled for remote JMX remote access.

The JMX properties (the JMX URL, username, and password) for the server were auto-discovered by the HQ Agent, or

entered manually, if necessary. If the HQ Agent auto-discovered the JMX properties, they appear on the Configuration

page for the server instance. If the agent did not discover the JMX properties, an authorized HQ user mustProperties

specify them on the server instance's page.Configuration Properties

For information on how to configure JMX remote see Sun's website ("

).hhttp://download.oracle.com/javase/1.5.0/docs/guide/management/agent.html"

Step 4 - Configure App Services as an Application in HQ

You may find it useful to configure an HQ application that groups the discovered services for an application.

Click in the HQ user interface.Resources->Browse

Select from the menu.New Application Tools

Enter a name for the application in the text box and click .Name OK

Click in the "Services" section of the page.Add to List

The left column on the page for the application lists all of the services in HQ that you have permission toEdit

view. The name of a discovered application service contains the name of the application, as specified in the

associated ModelMBean's ObjectName. (This is true only if the application name was specified in the

ObjectName.)

To filter the list by its application name or another identifying string, enter the string in the text box,Filter By Name

and click the green arrow.

Place a checkmark next to each service that belongs to the application, click the right arrow to move the services into

the right column, and click OK to add selected services to the application.

Model MBean Naming and Descriptor Data


Key Facts About ModelMBeans and Service Discovery (see page 28)

ModelMBean ObjectName Format (see page 29)

ModelMBeanInfo Descriptors (see page 29)

ModelMBeanAttributeInfo Descriptors (see page 29)

ModelMBeanOperationInfo Descriptors (see page 31)

This page specifies the descriptors that ModelMBeans must expose to enable a Hyperic Agent to discover and manage Java

application resources.

For information about Java service discovery feature and associated requirements, see .Java Applications (see page 25)

Key Facts About ModelMBeans and Service Discovery

Hyperic translates into service metadata, into custom property orModelMBeanInfo ModelMBeanAttributeInfo

metric metadata, and into control action metadata.ModelMBeanOperationInfo

hhttp://download.oracle.com/javase/1.5.0/docs/guide/management/agent.htmlhhttp://download.oracle.com/javase/1.5.0/docs/guide/management/agent.html

Page of 29 824

All MBean instances with the same type must have the same attributes, metrics, and operations. If the metadata for a

service type changes the type will be updated in Hyperic and any existing service instances will be deleted and

redeployed.

A service type cannot be deleted from Hyperic.

ModelMBean ObjectName Format

An ModelMBean's ObjectName must have this format:

spring.application:application=%application%,type=%type%,name=%name%*

where:

- (Optional) The name of the application that contains the resource. If defined, forms a portion of theapplication

service name in Hyperic.

- (Required) The Hyperic service type for the resource. When Hyperic creates the service to add to inventory, thistype

is the service type it will have. The value of also forms a portion of the service name in Hyperic.type

- (Required) An identifier that forms a portion of the name of the service in Hyperic. The service alsoname name

includes: name of the platform (machine) where the service runs, value of if specified, and the Hypericapplication

server type where the service runs. The order in which these components are concatenated into a name varies by the type

of server where the service runs.

For an MBean whose ObjectName is:

spring.application:application=swf-booking-mvc,type=MessageListener,name=bookingMessageListener

the Hyperic Agent creates a service in Hyperic whose:

Service type is "MessageListener"

Name is "Platform Name Apache Tomcat 6.0 swf-booking-mvc bookingMessageListener MessageListener"

ModelMBeanInfo Descriptors

ModelMBean Field Description Type Requirements Default Value

ModelMBeanInfo.

getDescription()

The friendly description of the service String Must not be null N/A

ModelMBeanInfo.

getMBeanDescriptor().

getField("typeName")

If supplied, supplies the service type for the

service to be created in Hyperic, overriding the

default value - the value of from thetype

service's ObjectName.

String Optional Value of the type

property in the

resource's

ObjectName,

described in

ModelMBean

ObjectName

Format (see page

29)

ModelMBeanInfo.

getMBeanDescriptor().

getField("export")

Can be used to prevent the Hyperic Agent from

creating a service for the MBean in Hyperic

inventory.

String Set to "true" or

"false"

"true"

Page of 30 824

ModelMBeanAttributeInfo Descriptors

The Hyperic Agent interprets ModelMBeanAttributeInfo as property or metric data. If the "metricType" descriptor is

defined, Hyperic interprets the data as a metric.

An attribute that represents a property must be JMX SimpleType or an array of JMX SimpleTypes.

An attribute that represents a metric must be numeric JMX SimpleType.

ModelMBean Field Description Type Expected Format Default

Value

ModelMBeanAttributeInfo.

getDescription()

Description of the

property or metric.

Note: In the Hyperic

user interface, a property

is identified by its

Description.

String Must not be null.

N/A


getDescriptor().

getField("metricCategory")

Category of a Metric String Allowable values:

PERFORMANCE - a metric that

provides time-related information. For

example, average elapsed time per

method call.

UTILIZATION - a metric that

indicates resource usage. For example,

memory usage, cache size, thread pool

size.

THROUGHPUT - a metric that

indicates the amount of work done

over a period of time. For example,

transactions per second.

UTILIZATION


getDescriptor().

getField("displayName")

Name that uniquely

identifies the metric for a

service type.

String This value is used to uniquely identify

the metric per service type.

Defaults to the

name of the

ModelMBean

attribute.

getDescriptor().

getField("indicator")

Designates a metric as an

Indicator in Hyperic.

Indicators are presented

on a resource's Indicator

page in Hyperic.

String If set to "true", the metric is an

Indicator, and is collected by default.

NOTE: If "false" metric will NOT be

collected by default.

"true"

Page of 31 824


getDescriptor().

getField("metricType")

Indicates how the value

of the metric changes

over time.

The presence of this field

indicates the

MBeanAttribute is a

metric. If not set, the

attribute will be

considered a custom

property.

Hyperic sets the

collection interval for a

metric based on the

value of metricType.

"counter" metrics are

collected every 10

minutes.

"gauge" metrics

arecollected every 5

minutes.

String The JMX specification requires

metricType have a value of either:

"counter" - a metric whose

value does not decrease unless

it is reset to a starting value.

"Number of requests received"

is an example of a counter

metric. Counter metrics

usually have a positive integer

value.

"gauge" - a metric whose value

can either increase or decrease.

"Cache Hit Rate" is an

example of a gauge metric.

"gauge"


getDescriptor().

getField("units")

The unit in which an

metric is measured.

String Hyperic specifies these allowable

values:

B - Bytes

KB - Kilobytes

MB - Megabytes

GB - Gigabytes

TB - Terabytes

epoch-millis - Time since

January 1, 1970 in

milliseconds.

epoch-seconds - Time since

January 1, 1970 in seconds.

ns - Nanoseconds

mu - Microseconds

ms - Milliseconds

jiffys - Jiffies (1/100 sec)

s - Seconds

cents - Cents (1/100 of 1 US

Dollar)

none

Defaults to

"none" if not

specified or if

set to an

unrecognized

unit.

ModelMBeanOperationInfo Descriptors

ModelMBean Operation return values and parameters should be JMX SimpleType or arrays of JMX SimpleTypes.

Page of 32 824

ModelMBean Field Description Type Expected Format Default Value

ModelMBeanOperationInfo.

getDescription()

The friendly description of the Operation String Must not be null. N/A

Page of 33 824

1.

2.

JBoss

Monitoring JBoss (see page 33)

JBoss Configuration Tracking (see page 33)

JBoss Metrics (see page 34)

Monitoring JBoss

You cannot manage a JBoss server on the same machine as the Hyperic Server.

JBoss 4.2 and later must run under Java 1.5 or later for Hyperic to be able to manage it.

The Hyperic Agent can usually discover the location of Jboss. If the agent fails to discover a JBoss server, the following

error occurs when you configure the server in Hyperic:

Invalid configuration: Plugin error: Plugin class not found:javax/management/MBeanException

(invalid classpath or corrupt plugin jar)

If the error occurs:

Add the property to the file for the agent. For usage, seejboss.installpath agent.properties

jboss.installpath.

Restart the Hyperic Agent.

JBoss Configuration Tracking

In Hyperic 4.6.5, the JBoss plugin uses a new plugin support class —--

--— that enables more detailed change tracking thanorg.hyperic.hq.product.FileChangeTrackPlugin

available in previous versions of Hyperic. This plugin tracks the change type ("add", "delete", "modify", or "rename") and

the actual changes in text files. For information about the new support class, see .FileChangeTrackPlugin

For JBoss, the default value of the field, which specifies which files to track is:Configuration Files

server/all/conf;true;.*\.xml|.*\.cfg|.*\.properties|.*\.ini|.*\.conf|.*\.config;,

server/default/conf;true;.*\.xml|.*\.cfg|.*\.properties|.*\.ini|.*\.conf|

.*\.config;,server/default/deploy;true;.*\.jar|.*\.dll|.*\.class|.*\.jsp|.*\.asp|

.*\.aspx|.*\.php|.*\.pl|.*\.vb|.*\.vbs|.*\.js|.*\.py|.*\.pyc|.*\.cgi|.*\.xml|.*\.cfg|

.*\.properties|.*\.ini|.*\.conf|.*\.config;,server/minimal/conf;true;.*\.xml|.*\.cfg|

.*\.properties|.*\.ini|.*\.conf|.*\.config;,server/standard/conf;true;.*\.xml|

.*\.cfg|.*\.properties|.*\.ini|.*\.conf|.*\.config;,server/web/conf;true;.*\.xml|

.*\.cfg|.*\.properties|.*\.ini|.*\.conf|.*\.config;,;false;jar-versions.xml;,

configuration/;false;.*\.xml|.*\.properties

4

Page of 34 824

When configuration tracking is enabled, this filter causes Hyperic to track files:

In any directory in the directory and any directories below it, files with theJBossHome/server/all/conf

following extensions: , , , , , .xml .cfg .properties .ini .conf .config

In any directory in the directory and any directories below it, files with theJBossHome/server/default/conf


In any directory in the directory and any directories below it, files withJBossHome/server/default/deploy

the following extensions: , , , , . , , , , , , , , .jar .dll .class .jsp .asp .aspx .php .pl .vb .vbs .js .py .pyc

, , , , , , .cgi .xml .cfg .properties .ini .conf .config

In any directory in the directory and any directories below it, files with theJBossHome/server/minimal/conf


In any directory in the directory and any directories below it, files with theJBossHome/server/standard/conf


In any directory in the directory and any directories below it, files with theJBossHome/server/web/conf


In the directory, the file JBossHome jar-versions.xml

In the directory, files with the following extensions: , ;JBossHome/configuration/ .xml .properties

Configuration tracking for Jboss is disabled by default. For information about how to enable configuration tracking and

how to specify which files to track, see Set Up Configuration Tracking for a Resource in .vFabric Hyperic Administration

JBoss Metrics

JBoss 7 server (see page 36)

JBoss 7 Datasource service (see page 38)

JBoss 7 Connector service (see page 41)

JBoss 7 deployment service (see page 40)

JBoss 7 Connector service (see page 41)

JBoss Managed 7 server (see page 41)

JBoss Managed 7 Connector service (see page 43)

JBoss Managed 7 Datasource service (see page 44)

JBoss Managed 7 deployment service (see page 46)

JBoss Host Controller 7 server (see page 46)

JBoss 6.0 server (see page 47)

JBoss 6.0 EJB 3 service (see page 48)

JBoss 6.0 Hibernate Session Factory service (see page 49)

JBoss 6.0 JCA Connection Pool service (see page 51)

JBoss 6.0 JCA Data Source service (see page 52)

JBoss 6.0 JGroups Channel service (see page 52)

JBoss 6.0 JMS HornetQ QUEUE service (see page 53)

JBoss 6.0 JMS HornetQ Topic service (see page 53)

JBoss 6.0 JMS QUEUE Destination service (see page 54)

JBoss 6.0 JMS Topic service (see page 55)

JBoss 6.0 Message Driven EJB service (see page 55)

JBoss 6.0 Stateful Session EJB service (see page 56)

JBoss 6.0 Stateless Session EJB service (see page 56)

JBoss 6.0 WebApp service (see page 57)

Page of 35 824


























JBoss 4.3 EJB3 service (see page 76)

JBoss 4.3 Entity EJB service (see page 76)





JBoss 4.3 JMS Destination service (see page 80)

JBoss 4.3 JMS Queue Destination service (see page 81)

















Page of 36 824





















JBoss 7 server

JBoss 7 server

NoLog Track Supported:

YesConfig Track Supported:

NoneCustom Properties Supported:

NoneSupported Control Actions:

Supported Metrics:

Name Alias Units Category Default

On

Default

Interval


thread-count thread-count none UTILIZATION false 5 min

peak-thread-count peak-thread-count none UTILIZATION false 5 min

total-started-thread-count total-started-thread-count none UTILIZATION false 5 min

daemon-thread-count daemon-thread-count none UTILIZATION false 5 min

current-thread-cpu-time current-thread-cpu-time ns UTILIZATION false 5 min

current-thread-user-time current-thread-user-time ns UTILIZATION false 5 min

Heap Used % h.used.p percentage UTILIZATION true 5 min

Heap Init h.init B UTILIZATION false 5 min

Heap used h.used B UTILIZATION false 5 min

Heap Commited h.committed B UTILIZATION false 5 min

Page of 37 824

Heap Max h.max B UTILIZATION false 5 min

Non-Heap Used % nh.used.p percentage UTILIZATION true 5 min

Non-Heap Init nh.init B UTILIZATION false 5 min

Non-Heap used nh.used B UTILIZATION false 5 min

Non-Heap Commited nh.committed B UTILIZATION false 5 min

Non-Heap Max nh.max B UTILIZATION false 5 min

Object Pending Finalization object-pending-finalization-count none UTILIZATION false 5 min

Aborted Transactions aborted-transactions none UTILIZATION false 10 min

Aborted Transactions per

Minute

aborted-transactions1m none UTILIZATION false 10 min

Application Transactions

Rollbacks

application-rollbacks none UTILIZATION false 10 min


Rollbacks per Minute

application-rollbacks1m none UTILIZATION false 10 min

Committed Transactions committed-transactions none UTILIZATION false 10 min

Committed Transactions per

Minute

committed-transactions1m none UTILIZATION false 10 min

Heuristics Transactions heuristics none UTILIZATION false 10 min

Heuristics Transactions per

Minute

heuristics1m none UTILIZATION false 10 min

Inflight Transactions inflight-transactions none UTILIZATION false 5 min

Nested Transactions nested-transactions none UTILIZATION false 10 min

Nested Transactions per Minute nested-transactions1m none UTILIZATION false 10 min

Resource Transactions

Rollbacks

resource-rollbacks none UTILIZATION false 10 min



resource-rollbacks1m none UTILIZATION false 10 min

Timed-out Transactions timed-out-transactions none UTILIZATION false 10 min

Timed-out Transactions per

Minute

timed-out-transactions1m none UTILIZATION true 10 min

Number of Transactions transactions none UTILIZATION false 10 min

Number of Transactions per

Minute

transactions1m none UTILIZATION true 10 min

Configuration help:

Page of 38 824

1.

2.

3.

4.

5.

Configure JBoss 7 for Monitoring

Config properties

: Management HTTP IP/HostName (usualy: localhost)addr

: Management HTTP Listen Portport

: Use https/sslhttps

: Administrator User nameuser

: Administrator User passwordpass

SSL Configuration Requirements (Hyperic 4.6 and later)

There are new SSL configuration requirements for secure communication between a Hyperic 4.6 agent and a JBoss.

If the property is (default value) in the file, the JBoss's unverifiedaccept.unverified.certificates false agent.properties

SSL certificate needs to be manually imported to a keystore that the Hyperic 4.6 agent can access. Otherwise, secure

communication between the Hyperic 4.6 agent and JBoss will fail.

If the property is in the file, the JBoss plugin will automaticallyaccept.unverified.certificates true agent.properties

import the unverified SSL certificate of the JBoss to the keystore accessible to the Hyperic 4.6 agent.This is not

because it is less secure and will expose the Hyperic agent to man-in-the-middle attacks.recommended

JBoss 7 Datasource service


NoConfig Track Supported:

Custom Properties Supported:

Name Description

jndi JNDI Name

driver Driver


Supported Metrics:


On

Availability Availability percentage AVAILABILITY true

ActiveCount ActiveCount none UTILIZATION true

AvailableCount AvailableCount none UTILIZATION true

AverageBlockingTime AverageBlockingTime ms UTILIZATION false

AverageCreationTime AverageCreationTime ms UTILIZATION false

CreatedCount CreatedCount none UTILIZATION false

CreatedCount per Minute CreatedCount1m none UTILIZATION false

DestroyedCount DestroyedCount none UTILIZATION false

Page of 39 824

DestroyedCount per Minute DestroyedCount1m none UTILIZATION false

MaxCreationTime MaxCreationTime ms UTILIZATION false

MaxUsedCount MaxUsedCount none UTILIZATION false

MaxUsedCount per Minute MaxUsedCount1m none UTILIZATION false

MaxWaitCount MaxWaitCount none UTILIZATION false

MaxWaitCount per Minute MaxWaitCount1m none UTILIZATION false

MaxWaitTime MaxWaitTime ms UTILIZATION true

PreparedStatementCacheAccessCount PreparedStatementCacheAccessCount none UTILIZATION false

PreparedStatementCacheAccessCount

per Minute

PreparedStatementCacheAccessCount1m none UTILIZATION false

PreparedStatementCacheAddCount PreparedStatementCacheAddCount none UTILIZATION false

PreparedStatementCacheAddCount

per Minute

PreparedStatementCacheAddCount1m none UTILIZATION false

PreparedStatementCacheCurrentSize PreparedStatementCacheCurrentSize none UTILIZATION false

PreparedStatementCacheCurrentSize

per Minute

PreparedStatementCacheCurrentSize1m none UTILIZATION false

PreparedStatementCacheDeleteCount PreparedStatementCacheDeleteCount none UTILIZATION false

PreparedStatementCacheDeleteCount

per Minute

PreparedStatementCacheDeleteCount1m none UTILIZATION false

PreparedStatementCacheHitCount PreparedStatementCacheHitCount none UTILIZATION false

PreparedStatementCacheHitCount per

Minute

PreparedStatementCacheHitCount1m none UTILIZATION true

PreparedStatementCacheMissCount PreparedStatementCacheMissCount none UTILIZATION false

PreparedStatementCacheMissCount

per Minute

PreparedStatementCacheMissCount1m none UTILIZATION true

TimedOut TimedOut none UTILIZATION false

TimedOut per Minute TimedOut1m none UTILIZATION false

TotalBlockingTime TotalBlockingTime ms UTILIZATION false

TotalCreationTime TotalCreationTime ms UTILIZATION false

Configuration help:

JBoss 7 Connector service




Page of 40 824

Name Description

protocol protocol

scheme scheme


Supported Metrics:

Name Alias Units Category Default On Default Interval


errorCount errorCount none UTILIZATION false 10 min

errorCount per Minute errorCount1m none UTILIZATION true 10 min

requestCount requestCount none UTILIZATION false 10 min

requestCount per Minute requestCount1m none UTILIZATION true 10 min

maxTime maxTime ms UTILIZATION true 5 min

bytesSent bytesSent none UTILIZATION false 10 min

bytesSent per Minute bytesSent1m none UTILIZATION false 10 min

bytesReceived bytesReceived none UTILIZATION false 10 min

bytesReceived per Minute bytesReceived1m none UTILIZATION false 10 min

processingTime processingTime ms UTILIZATION false 10 min

processingTime per Minute processingTime1m ms UTILIZATION false 10 min

Configuration help:

JBoss 7 deployment service




Name Description

runtime-name runtime-name


Supported Metrics:



Page of 41 824

Configuration help:

JBoss 7 Connector service




Name Description

protocol protocol

scheme scheme


Supported Metrics:














Configuration help:

JBoss Managed 7 server

JBoss Managed 7 server





Supported Metrics:

Page of 42 824


On

Default

Interval


















Object Pending Finalization object-pending-finalization-count none UTILIZATION false 5 min

Aborted Transactions aborted-transactions none UTILIZATION false 10 min

Aborted Transactions per

Minute

aborted-transactions1m none UTILIZATION false 10 min


Rollbacks

application-rollbacks none UTILIZATION false 10 min



application-rollbacks1m none UTILIZATION false 10 min

Committed Transactions committed-transactions none UTILIZATION false 10 min

Committed Transactions per

Minute

committed-transactions1m none UTILIZATION false 10 min

Heuristics Transactions heuristics none UTILIZATION false 10 min

Heuristics Transactions per

Minute

heuristics1m none UTILIZATION false 10 min

Inflight Transactions inflight-transactions none UTILIZATION false 5 min

Page of 43 824

1.

2.

3.

4.

5.

6.

7.

Nested Transactions nested-transactions none UTILIZATION false 10 min

Nested Transactions per Minute nested-transactions1m none UTILIZATION false 10 min


Rollbacks

resource-rollbacks none UTILIZATION false 10 min



resource-rollbacks1m none UTILIZATION false 10 min

Timed-out Transactions timed-out-transactions none UTILIZATION false 10 min

Timed-out Transactions per

Minute

timed-out-transactions1m none UTILIZATION true 10 min

Number of Transactions transactions none UTILIZATION false 10 min

Number of Transactions per

Minute

transactions1m none UTILIZATION true 10 min

Configuration help:

Configure JBoss 7 Managed for Monitoring

Config properties






: Host Controller Namehost

: Server Nameserver









JBoss Managed 7 Connector service




Page of 44 824

Name Description

protocol protocol

scheme scheme


Supported Metrics:














Configuration help:

JBoss Managed 7 Datasource service




Name Description

jndi JNDI Name

driver Driver


Supported Metrics:


On

Page of 45 824

Availability Availability percentage AVAILABILITY true

ActiveCount ActiveCount none UTILIZATION true

AvailableCount AvailableCount none UTILIZATION true

AverageBlockingTime AverageBlockingTime ms UTILIZATION false

AverageCreationTime AverageCreationTime ms UTILIZATION false

CreatedCount CreatedCount none UTILIZATION false

CreatedCount per Minute CreatedCount1m none UTILIZATION false

DestroyedCount DestroyedCount none UTILIZATION false

DestroyedCount per Minute DestroyedCount1m none UTILIZATION false

MaxCreationTime MaxCreationTime ms UTILIZATION false

MaxUsedCount MaxUsedCount none UTILIZATION false

MaxUsedCount per Minute MaxUsedCount1m none UTILIZATION false

MaxWaitCount MaxWaitCount none UTILIZATION false

MaxWaitCount per Minute MaxWaitCount1m none UTILIZATION false

MaxWaitTime MaxWaitTime ms UTILIZATION true

PreparedStatementCacheAccessCount PreparedStatementCacheAccessCount none UTILIZATION false

PreparedStatementCacheAccessCount

per Minute

PreparedStatementCacheAccessCount1m none UTILIZATION false

PreparedStatementCacheAddCount PreparedStatementCacheAddCount none UTILIZATION false

PreparedStatementCacheAddCount

per Minute

PreparedStatementCacheAddCount1m none UTILIZATION false

PreparedStatementCacheCurrentSize PreparedStatementCacheCurrentSize none UTILIZATION false

PreparedStatementCacheCurrentSize

per Minute

PreparedStatementCacheCurrentSize1m none UTILIZATION false

PreparedStatementCacheDeleteCount PreparedStatementCacheDeleteCount none UTILIZATION false

PreparedStatementCacheDeleteCount

per Minute

PreparedStatementCacheDeleteCount1m none UTILIZATION false

PreparedStatementCacheHitCount PreparedStatementCacheHitCount none UTILIZATION false

PreparedStatementCacheHitCount per

Minute

PreparedStatementCacheHitCount1m none UTILIZATION true

PreparedStatementCacheMissCount PreparedStatementCacheMissCount none UTILIZATION false

PreparedStatementCacheMissCount

per Minute

PreparedStatementCacheMissCount1m none UTILIZATION true

TimedOut TimedOut none UTILIZATION false

Page of 46 824

TimedOut per Minute TimedOut1m none UTILIZATION false

TotalBlockingTime TotalBlockingTime ms UTILIZATION false

TotalCreationTime TotalCreationTime ms UTILIZATION false

Configuration help:

JBoss Managed 7 deployment service




Name Description

runtime-name runtime-name


Supported Metrics:



Configuration help:

JBoss Host Controller 7 server

JBoss Host Controller 7 server





Supported Metrics:


On

Default

Interval







Page of 47 824

1.

2.

3.

4.

5.

6.












Configuration help:

Configure JBoss 7 Host Controller for Monitoring

Config properties






: Host Controller Namehost









Page of 48 824

JBoss 6.0 server

JBoss 6.0 server

YesLog Track Supported:



Name Description

version JBoss Version

JavaVersion Java Version

JavaVendor Java Vendor

BuildDate Build Date

VersionName Version Name

stop,start,restart,runGarbageCollectorSupported Control Actions:

Supported Metrics:


On

Default

Interval


Active Thread Count ActiveThreadCount none THROUGHPUT true 5 min

Active Thread Group Count ActiveThreadGroupCount none THROUGHPUT false 5 min

JVM Free Memory FreeMemory B UTILIZATION false 5 min

JVM Total Memory TotalMemory B UTILIZATION true 5 min

JVM Max Memory MaxMemory B UTILIZATION false 30 min

Transactions Active TxCount none UTILIZATION false 5 min

Transactions Committed TxCommits none UTILIZATION false 10 min

Transactions Committed per

Minute

TxCommits1m none UTILIZATION false 10 min

Transactions Rolledback TxRollbacks none UTILIZATION false 10 min

Transactions Rolledback per

Minute

TxRollbacks1m none UTILIZATION false 10 min

Configuration help:

Page of 49 824

JBoss 6.0 EJB 3 service




stop,startSupported Control Actions:

Supported Metrics:



Configuration help:

JBoss 6.0 Hibernate Session Factory service





Supported Metrics:


On

Default

Interval


Entity Insert Count EntityInsertCount none THROUGHPUT false 10 min

Entity Insert Count per

Minute

EntityInsertCount1m none THROUGHPUT true 10 min

Query Execution Max Time QueryExecutionMaxTime ms PERFORMANCE true 5 min

Entity Update Count EntityUpdateCount none THROUGHPUT false 10 min

Entity Update Count per

Minute

EntityUpdateCount1m none THROUGHPUT false 10 min

Collection Update Count CollectionUpdateCount none THROUGHPUT false 10 min

Collection Update Count per

Minute

CollectionUpdateCount1m none THROUGHPUT false 10 min

Entity Load Count EntityLoadCount none THROUGHPUT false 10 min

Entity Load Count per

Minute

EntityLoadCount1m none THROUGHPUT false 10 min

Entity Fetch Count EntityFetchCount none THROUGHPUT false 10 min

Entity Fetch Count per

Minute

EntityFetchCount1m none THROUGHPUT true 10 min

Page of 50 824

Entity Delete Count EntityDeleteCount none THROUGHPUT false 10 min

Entity Delete Count per

Minute

EntityDeleteCount1m none THROUGHPUT false 10 min

Collection Recreate Count CollectionRecreateCount none THROUGHPUT false 10 min

Collection Recreate Count

per Minute

CollectionRecreateCount1m none THROUGHPUT false 10 min

Query Execution Count QueryExecutionCount none THROUGHPUT false 10 min

Query Execution Count per

Minute

QueryExecutionCount1m none THROUGHPUT true 10 min

Flush Count FlushCount none THROUGHPUT false 10 min

Flush Count per Minute FlushCount1m none THROUGHPUT false 10 min

Collection Load Count CollectionLoadCount none THROUGHPUT false 10 min

Collection Load Count per

Minute

CollectionLoadCount1m none THROUGHPUT false 10 min

Successful Transaction Count SuccessfulTransactionCount none THROUGHPUT false 10 min

Successful Transaction Count

per Minute

SuccessfulTransactionCount1m none THROUGHPUT false 10 min

Query Cache Hit Count QueryCacheHitCount none THROUGHPUT false 10 min

Query Cache Hit Count per

Minute

QueryCacheHitCount1m none THROUGHPUT false 10 min

Collection Remove Count CollectionRemoveCount none THROUGHPUT false 10 min

Collection Remove Count per

Minute

CollectionRemoveCount1m none THROUGHPUT false 10 min

Connect Count ConnectCount none THROUGHPUT

vFabric Hyperic Resource Configuration and Metrics...2008/06/05 · SpringSource tc Runtime 7.0...

Documents

Transcript of vFabric Hyperic Resource Configuration and Metrics...2008/06/05 · SpringSource tc Runtime 7.0...