LATEST VERSION: 3.2 - CHANGELOG
Pivotal tc Server v3.2

Monitoring tc Runtime Instances Using Hyperic

Note: VMware vRealize Hyperic has an End of General Support date of December 31st, 2017

VMware vRealize Hyperic monitors operating systems, middleware, and applications running in physical, virtual and cloud environments. For information on vRealize Hyperic, including Hyperic Server installation instructions, see the VMware vRealize Hyperic documentation.

Two versions of the Hyperic Agent plugin are available:

tc Runtime 8 Plugin

Pivotal provides a new Hyperic Agent plugin for tc Runtime 8 to monitor your instances of Pivotal tc Server on any computer, all Spring-powered applications, and a variety of other platforms and application servers such as Apache Tomcat using VMware vRealize Hyperic Server. Hyperic provides a single console with powerful dashboards from which you can easily check the health of your applications. The capability to manage tc Server instances is not available.

With Hyperic Server you can:

  • Manage the lifecycle of tc Runtime instances by starting, stopping, and restarting local or remote instances.

In addition to the preceding tc Runtime-related actions, Hyperic performs these standard tasks:

  • Inventories the resources on your network.
  • Monitors your resources.
  • Alerts you to problems with resources.
  • Controls the resources.

User Permissions Required to Use the tc Server Hyperic Plug-in Features

For simplicity, it is often assumed in this documentation that you log in to the Hyperic user interface as the Hyperic super-user (hqadmin) when you want to manage a tc Runtime instance. This is not required, of course. You can also log in as a non-super user and still use the tc Server Hyperic plugin features, as long as the user has the correct permissions.

In Hyperic, users are assigned roles, which in turn are assigned a permission level (None, Read-Only, Read-Write, or Full) to each Hyperic inventory type (platforms, servers, services, groups, and applications) For general information about what each permission means with respect to server resources (such as a tc Runtime instance) in Hyperic, see “Creating and Managing Roles in vRealize Hyperic” in the VMware vRealize Hyperic documentation. For general information about the default users in Hyperic and creating new ones, see “Creating and Managing User Accounts.”

The following table describes the additional effects that some of the Hyperic permissions have on the tc Server Hyperic plugin features. Use this table to determine which role you should assign a user that will be managing tc Runtime instances.

Table 1. Hyperic Permission Effects on tc Server Hyperic Plug-in Features
Permission Additional Effect on tc Server Hyperic Plug-in Features
Read-Only Allows the user to view instances of the type, but not create, edit, or delete them. For Platforms, Servers, Services, Groups, also enables Read-Only access to alert definitions for the inventory type.
Read-Write Allows the user to view and edit instances of the type, but not create or delete them.

For Platforms, Servers, Services, Groups, provides Full access to alert definitions for the inventory type; permission to manage alerts (enable/disable, fix, acknowledge) for the inventory type; and permission to perform supported control operations on resources of the inventory type.

Full Allows users to create, edit, delete, and view instance of the type.

For Platforms, Servers, Services, Groups, provides Full access to alert definitions for the inventory type; permission to manage alerts (enable/disable, fix, acknowledge) for the inventory type; and permission to perform supported control operations on resources of the inventory type.

tc Server includes a full set of diagnostic features that make it easy to troubleshoot problems with tc Runtime instances and the applications that you deploy to them. For each diagnostic feature, the tc Server Hyperic plug-in has one or more corresponding preconfigured alerts.

After Hyperic triggers an alert associated with a diagnostic feature (because the associated condition has been met), Hyperic disables the alert until an administrator marks it as Fixed. You can use Hyperic to further configure this alert with additional control actions or even disable it, as described in the following sections:

Viewing and Changing the Preconfigured Alerts

The preconfigured Hyperic alerts associated to the diagnostic features of tc Runtime work on one of two Hyperic resources: either the tc Runtime instance itself, or with a service of the tc Runtime instance. This information is important to know because it determines how you view, and optionally change, a particular alert.

The following table lists each preconfigured alert and the Hyperic resource type to which it is associated. The resource type SpringSource tc Runtime 7.0 refers to the tc Runtime instance itself; the resource type SpringSource tc Runtime 7.0 Service, such as SpringSource tc Runtime 7.0 Thread Diagnostics, refers to a service of the tc Runtime instance.

Note: The tc Runtime version is associated with the core version of Tomcat on which the runtime is based, rather than the version of the tc Server bundle.

The third column in the table indicates whether the alert is triggered by a metric condition or an event/log level condition. If the former, the name of the metric is displayed; if the latter, the specific string in the log (if any) that triggers the alert is displayed.

Table 2. Preconfigured tc Runtime Alerts

Alert Name Associated Hyperic Resource Type Metric or Events/Log Level Based?
Deadlocks Detected SpringSource tc Runtime 7.0 and Pivotal tc Runtime 8.0 Metric (Deadlocks Detected)
Excessive Time Spent in Garbage Collection SpringSource tc Runtime 7.0 and Pivotal tc Runtime 8.0 Metric (Percent Up Time in Garbage Collection)
Slow or Failed Request SpringSource tc Server 7.0 Thread Diagnostics and Pivotal tc Server 8.0 Thread Diagnostics Events/Logs Level.
JDBC Connection Abandoned SpringSource tc Server 7.0 Tomcat JDBC Connection Pool Global and Pivotal tc Server 8.0 Tomcat JDBC Connection Pool Global Events/Logs Level (CONNECTION ABANDONED)
JDBC Connection Failed SpringSource tc Server 7.0 Tomcat JDBC Connection Pool Global and Pivotal tc Server 8.0 Tomcat JDBC Connection Pool Global Events/Logs Level (CONNECTION FAILED)
JDBC Query Failed SpringSource tc Server 7.0 Tomcat JDBC Connection Pool Global and Pivotal tc Server 8.0 Tomcat JDBC Connection Pool Global Events/Logs Level (FAILED QUERY)
Slow JDBC Query SpringSource tc Server 7.0 Tomcat JDBC Connection Pool Global and Pivotal tc Server 8.0 Tomcat JDBC Connection Pool Global Events/Logs Level (SLOW QUERY)

The following procedure summarizes how to view and change preconfigured alerts. For a detailed tutorial that shows how to view and change the Deadlocks Detected alert, see “Tutorial: Using Hyperic to Configure and Manage tc Runtime Instances” in Getting Started with Pivotal tc Server.

  1. Browse to the resource to which the alert is associated, as described in the preceding table. See “Getting Started with the Hyperic User Interface” in Getting Started with Pivotal tc Server for information about browsing to Hyperic resources.
  2. Click the Alert tab.
  3. Click the Configure button. A table of alerts currently configured for the resource is displayed.
  4. Click the name of the alert. The Alert Definition page for the alert is displayed.

    The definition page has three sections: the top Alert Properties section provides general properties of the alert; the middle Condition Set section describes the conditions that trigger the alert; and a series of tabs at the bottom enable you to configure the particular control action that occurs if the alert is triggered, the escalation scheme, who should be notified if the alert is triggered, and so on.

  5. If you want to change the general properties, conditions, control actions, and so on of the alert, click the appropriate EDIT… button, make your changes, then click OK.

  6. To disable the alert, go back to the Alert Definitions table, select the name of the alert by checking the box to the left of its name, then select No for the Set Active drop-down list and click the arrow to the right.

The remainder of this chapter describes each alert in more detail, including any special instructions to enable the alert.

Viewing and Changing the Metric Collection Interval

As shown in the Preconfigured tc Runtime Alerts table, the two alerts associated with the tc Runtime instance itself use metrics in their condition to determine whether the alert should be triggered. The following procedure describes how you can view, and optionally change, the collection interval for Deadlock Detection and Excessive Time in Garbage Collection.

  1. Click the Administration tab at the top of the Hyperic user interface.
  2. In the Hyperic Server Settings section, click the Monitoring Defaults link.
  3. Scroll down until you find the SpringSource tc Runtime 7.0 or SpringSource tc Runtime 8.0 entry in the Server Types table, and then click the EDIT TEMPLATE METRIC link to the right.

    A page shows all metrics associated with the tc Runtime instance. For example, under Utilization you will find the Deadlocks Detected metric. By default, the Collection Interval column shows that Hyperic Server collects information about this metric every 2 minutes.

  4. To change the collection interval for a specific metric, select it by clicking the box to the left of its name.

  5. Enter the new collection interval at the bottom of the page in the Collection Interval for Selected field, specify whether it is in minutes or hours, then click the arrow to the right.

Deadlock Detection

The tc Runtime automatically detects whether a thread deadlock occurs in a tc Runtime instance or an application deployed to the instance.

The out-of-the-box Hyperic alert is triggered if the Deadlocks Detected metric exceeds 0. Hyperic checks the metric every two minutes to see whether the condition is met. Hyperic applies this alert to all auto-discovered tc Runtime instances and enables it by default. This alert is associated with the tc Runtime instance itself.

For a detailed tutorial that shows how to view and change the Deadlocks Detected alert, see “Tutorial: Using Hyperic to Configure and Manage tc Runtime Instances” in Getting Started with Pivotal tc Server.

Excessive Time in Garbage Collection

A Hyperic metric represents the percentage of process up time (0 -100) that the tc Runtime instance has spent in garbage collection.

The alert is triggered when the total garbage collection time is excessive (by default, 40% of process up time.) Hyperic checks this metric every 5 minutes to see if the condition has been met. Hyperic applies this alert to all auto-discovered tc Runtime instances and enables it by default.

Enabling the Slow or Failed Request Alert

When clients begin connecting and using a Web application deployed to a tc Runtime instance, they may encounter slow or failed requests. Although the tc Runtime instance logs these errors in the log files by default, it is often difficult to pinpoint the exact origin of the error and how to go about fixing it. By enabling thread diagnostics, tc Runtime provides additional information to help you troubleshoot the problem.

A failed request is one that simply did not execute; a slow request is a request that takes longer than a certain threshold. The default threshold is 500 milliseconds.

When you enable thread diagnostics, you can view the following contextual information about a slow or failed client request:

  • Time and date of the slow or failed request.
  • Exact URL invoked by the client that resulted in a slow or failed request.
  • Exact error returned by the request.
  • Database queries that were executed as part of the request and how long each one took.
  • Whether any database connection failed or succeeded.
  • Whether the database had any other connectivity problems.
  • Whether the database connection pool ran out of connections.
  • Whether any garbage collection occurred during the request, and if so, how long it took.

The associated Hyperic alert is triggered if a client request to tc Runtime is slow (over a configured threshold) or if it failed.

This alert is not enabled by default.

Enabling JDBC Connection Monitoring

Hyperic includes a service called SpringSource tc Runtime 7.0 Tomcat JDBC Connection Pool Global that represents any high-concurrency Tomcat JDBC datasources you might have configured for your tc Runtime instance. This service monitors the health of the datasource, such as whether its connection to the database has failed or was abandoned, and whether the JDBC queries that clients execute are taking too long. Hyperic creates this service when you create a new Tomcat JDBC datasource; one instance of a service exists per datasource.

Four Hyperic alerts are associated with this diagnostic feature; they are triggered as follows:

  • JDBC Connection Failed: A particular high-concurrency JDBC connection that uses a configured datasource fails.
  • JDBC Connection Abandoned: A particular high-concurrency JDBC connection that uses a configured datasource is abandoned by the database server.
  • JDBC Query Failed: A high-concurrency JDBC query fails.
  • Slow JDBC Query: A high-concurrency JDBC query takes too long to execute.

To receive monitoring information for the preceding JDBC alerts, enable log tracking for this service:

  1. Browse to the SpringSource tc Runtime 7.0 Tomcat JDBC Connection Pool Global service associated with your JDBC datasource.
  2. Click the Inventory tab.
  3. In the Configuration Properties section, be sure that the service.log_track.enable property is checked. Checking this box subscribes Hyperic to JMX notifications sent from the tc Runtime instance, which then get displayed in Hyperic as log events.

Hyperic tc Server Plugin Metrics

The table below defines the metrics that the Hyperic plugin for tc Server reports. The following information is listed for each metric:

  • Attribute/Metric Name. The name of a metric is typically the same as the MBean attribute that provides the metric value.
  • Units. The units in which the metric is reported.
  • Detection. The MBean from which the metric is obtained, or the process by which it is obtained.
  • On/Off. Indicates whether the plugin, by default, reports the metric.
  • Description.
  • Category. The Hyperic service type or top level server type to which the metric applies.
Table 3. Metric Definitions
Metric/Attribute Name Units Detection On/Off Description Category
ThreadCount ms java.lang:​type=Threading Off Thread Count Thread
CurrentThreadCpuTime ms java.lang:​type=Threading Off

CPU Time used by the current thread

Thread

CurrentThread User Time

ms java.lang:​type=Threading Off Time the current thread executed in user mode Thread

Daemon Thread Count

  java.lang:​type=Threading Off Number of daemon threads Thread

Peak Thread Count

  java.lang:​type=Threading Off Highest amount of threads executing Thread

Total Started Thread Count

  java.lang:​type=Threading Off Total number of threads that have been created or started during life of VM. Thread
FreeSwapSpaceSize B java.lang:​type=Threading Off The amount of free swap space Operating System
FreePhysicalMemorySize B java.lang:​type=OperatingSystem Off The amount of free physical memory Operating System
ProcessCpuTime ns java.lang:​type=OperatingSystem Off Time the CPU has spent executing the process Operating System
OpenFileDescriptorCount   java.lang:​type=OperatingSystem Off Number of open file descriptor for the process Operating System
SystemLoadAverage   java.lang:​type=OperatingSystem Off The average system load Operating System
Uptime ms java.lang:​type=OperatingSystem On Time the process has been running Runtime
DataSource Context Availability   Tc Runtime 7.0.x: ${domain}:type=​DataSource,context=​*,host=*,class=​javax.sql.DataSource,name=*

Tc Runtime 8.0.x: ${domain}:type=​DataSource,context=​*,host=*,class=​javax.sql.DataSource,name=*

On Availability of the DataSource Context DataSource Context
DataSource Context numActive   Tc Runtime 7.0.x: ${domain}:type=​DataSource,context=​*,host=*,class=​javax.sql.DataSource,name=*

Tc Runtime 8.0.x: ${domain}:type=​DataSource,context=​*,host=*,class=​javax.sql.DataSource,name=*

On Current number of active connections DataSource Context
DataSource Context numIdle   Tc Runtime 7.0.x: ${domain}:type=​DataSource,context=​*,host=*,class=​javax.sql.DataSource,name=*

Tc Runtime 8.0.x: ${domain}:type=​DataSource,context=​*,host=*,class=​javax.sql.DataSource,name=*

On Current number of idle connections DataSource Context
DataSource Context maxOpenPreparedStatements   Tc Runtime 7.0.x: ${domain}:type=​DataSource,context=​*,host=*,class=​javax.sql.DataSource,name=*

Tc Runtime 8.0.x: ${domain}:type=​DataSource,context=​*,host=*,class=​javax.sql.DataSource,name=*

Off Maximum Opened Prepared Statements DataSource Context
DataSource Context maxWait   Tc Runtime 7.0.x: ${domain}:type=​DataSource,context=​*,host=*,class=​javax.sql.DataSource,name=*

Tc Runtime 8.0.x: ${domain}:type=​DataSource,context=​*,host=*,class=​javax.sql.DataSource,name=*

Off Maximum Wait DataSource Context
DataSource Context percentActiveConnections   Tc Runtime 7.0.x: ${domain}:type=​DataSource,context=​*,host=*,class=​javax.sql.DataSource,name=*

Tc Runtime 8.0.x: ${domain}:type=​DataSource,context=​*,host=*,class=​javax.sql.DataSource,name=*

Off Percentage of Active Connections DataSource Context
Manager Availability   Tc Runtime 7.0.x: ${domain}:type=​Manager,context=*,host=*

Tc Runtime 8.0.x: ${domain}:type=​Manager,context=*,host=*

On Availability of the Manager mbean Manager
activeSessions   Tc Runtime 7.0.x: ${domain}:type=​Manager,context=*,host=*

Tc Runtime 8.0.x: ${domain}:type=​Manager,context=*,host=*

Off Active Sessions Manager
expiredSessions   Tc Runtime 7.0.x: ${domain}:type=​Manager,context=*,host=*

Tc Runtime 8.0.x: ${domain}:type=​Manager,context=*,host=*

Off Expired Sessions Manager
maxActive   Tc Runtime 7.0.x: ${domain}:type=​Manager,context=*,host=*

Tc Runtime 8.0.x: ${domain}:type=​Manager,context=*,host=*

Off Maximum Active Sessions Manager
processingTime sec Tc Runtime 7.0.x: ${domain}:type=​Manager,context=*,host=*

Tc Runtime 8.0.x: ${domain}:type=​Manager,context=*,host=*

Off Processing time per session Manager
rejectedSessions   Tc Runtime 7.0.x: ${domain}:type=​Manager,context=*,host=*

Tc Runtime 8.0.x: ${domain}:type=​Manager,context=*,host=*

Off Rejected Sessions Manager
sessionAverageAliveTime   Tc Runtime 7.0.x: ${domain}:type=​Manager,context=*,host=*

Tc Runtime 8.0.x: ${domain}:type=​Manager,context=*,host=*

Off Session Average Alive Time Manager
sessionCounter   Tc Runtime 7.0.x: ${domain}:type=​Manager,context=*,host=*

Tc Runtime 8.0.x: ${domain}:type=​Manager,context=*,host=*

Off Session Counter Manager
sessionCreateRate   Tc Runtime 7.0.x: ${domain}:type=​Manager,context=*,host=*

Tc Runtime 8.0.x: ${domain}:type=​Manager,context=*,host=*

Off Sessions Created per minute Manager
sessionExpireRate   Tc Runtime 7.0.x: ${domain}:type=​Manager,context=*,host=*

Tc Runtime 8.0.x: ${domain}:type=​Manager,context=*,host=*

Off Sessions Destroyed per minute Manager
sessionMaxAliveTime sec Tc Runtime 7.0.x: ${domain}:type=​Manager,context=*,host=*

Tc Runtime 8.0.x: ${domain}:type=​Manager,context=*,host=*

Off Session Max Alive Time Manager
HeapMemoryUsage.used B java.lang:​type=Memory On Heap Memory Used Memory
HeapMemoryUsage.committed B java.lang:​type=Memory On Heap Memory Committed Memory
HeapMemoryUsage.max B java.lang:​type=Memory On Heap Memory Maximum Memory
HeapMemory.free B java.lang:​type=Memory (calculated from max-used) On The calculated amount of free memory Memory
deadLockedThreadCount   JMX Notification On The number of deadlocks detected on instance Deadlock Notification
tc Runtime Availability   Process scan On

Detection of tc Runtime availability

Availability
percentUpTimeSpent   Calculation of garbage collection from mbeans On

% of time spent in garbage collection

Garbage Collection
Thread Diagnostics Context Availability   Mbean scan:​tcServer:type=Serviceability,​name=DiagnosticsValve,context=*​,host=*,engine=* On Detection of Thread Diagnostics Context on DiagnosticsValve Thread Diagnostics
Thread Diagnostics Engine Availability   tcServer:type=​Serviceability,name=​DiagnosticsValve,engine=* On Detection of Thread Diagnostics Context on DiagnosticsValve Thread Diagnostics
Thread Diagnostics Host Availability   tcServer:type=​Serviceability,name=​DiagnosticsValve,host=​*,engine=* On Detection of Thread Diagnostics Context on DiagnosticsValve Thread Diagnostics

DataSource Global Availability

  Catalina:type=​DataSource,class=​javax.sql.DataSource,name=* On   DataSource Global
DataSource Global numActive   Catalina:type=​DataSource,class=​javax.sql.DataSource,name=* On

Current number of active connections

DataSource Global
DataSource Global numIdle   Catalina:type=​DataSource,class=​javax.sql.DataSource,name=* On

Current number of idle connections

DataSource Global
DataSource Global maxOpenPreparedStatements   Catalina:type=​DataSource,class=​javax.sql.DataSource,name=* Off

Maximum Opened Prepared Statements

DataSource Global
DataSource Global maxWait ms Catalina:type=​DataSource,class=​javax.sql.DataSource,name=* Off

Maximum Wait

DataSource Global
DataSource Global percentActiveConnections   Catalina:type=​DataSource,class=​javax.sql.DataSource,name=* Off

Percentage of Active Connections

DataSource Global
Tomcat JDBC Connection Pool Context Availability  

Tc Runtime 7.0.x:​ tomcat.jdbc:name=​*,context=​*,type=ConnectionPool,host=​*,class=*

Tc Runtime 8.0.x: tomcat.jdbc:name=​*,context=​*,type=ConnectionPool,host=​*,class=*

On

Detection of Connection pool context

Tomcat JDBC Connection Pool
Tomcat JDBC Connection Pool Global  

java.lang:​type=​GarbageCollector,name=*

On

Detection of Connection pool global

Tomcat JDBC Connection Pool
Collection Count  

java.lang:​type=​GarbageCollector,name=*

Off

Collection Count of GCs

Garbage Collector
Collection Time  

${domain}:j2eeType=WebModule,name=​*,J2EEApplication=*,J2EEServer=*

Off

Collection Time of GCs

Garbage Collector
Web Module Availability  

${domain}:j2eeType=WebModule,name=​*,J2EEApplication=​*,J2EEServer=*

On Availability of each webapp deployed Web Module Stats
processingTime sec ${domain}:type=​ThreadPool,name=* On Processing time of each webapp Web Module Stats
Thread Pools Availability   ${domain}:type=​ThreadPool,name=* On Availability of the Thread Pool configured Thread Pool
currentThreadCount   ${domain}:type=​ThreadPool,name=* On The current thread count of the ThreadPool Thread Pool
currentThreadBusy   ${domain}:type=​ThreadPool,name=* On The current count of busy threads in the pool Thread Pool
percentAllocatedThread   ${domain}:type=​ThreadPool,name=* Off Percentage of the allocated threads Thread Pool
percentActiveThreads   ${domain}:type=​ThreadPool,name=* Off Percentage of active threads Thread Pool
Executor Availability   ${domain}:type=​Executor,name=* On Availability of the Executor mbean Executor
maxThreads   ${domain}:type=​Executor,name=* On Max number of threads in the executor Executor
poolSize   ${domain}:type=​Executor,name=* On The current size of the pool of threads Executor
activeCount   ${domain}:type=​Executor,name=* On The active threads in the pool Executor
queueSize   ${domain}:type=​Executor,name=* On Size of the queue for the pool Executor
Servlet Availability   ${domain}:j2eeType=​Servlet,name=​*,WebModule=​*,J2EEApplication=​*,J2EEServer=​* On Availability of the Servlet Servlet Monitor
classLoadTime   ${domain}:j2eeType=​Servlet,name=​*,WebModule=​*,J2EEApplication=​*,J2EEServer=​* Off Class load time Servlet Monitor
errorCount   ${domain}:j2eeType=​Servlet,name=​*,WebModule=​*,J2EEApplication=​*,J2EEServer=​* On Error count on the servlet Servlet Monitor
loadTime   ${domain}:j2eeType=​Servlet,name=​*,WebModule=​*,J2EEApplication=​*,J2EEServer=​* Off Error count on the servlet Servlet Monitor
processingTime   ${domain}:j2eeType=​Servlet,name=​*,WebModule=​*,J2EEApplication=​*,J2EEServer=​* On Processing time of the servlet Servlet Monitor
requestCount   ${domain}:j2eeType=​Servlet,name=​*,WebModule=​*,J2EEApplication=​*,J2EEServer=​* On The number of requests on the servlet Servlet Monitor
JSP Monitor Availability   ${domain}:type=​​JspMonitor,name=​jsp,WebModule=​*,J2EEApplication=​*,J2EEServer=​* On Availability of the JSPMonitor mbean JSP Monitor
jspCount   ${domain}:type=​​JspMonitor,name=​jsp,WebModule=​*,J2EEApplication=​*,J2EEServer=​* On The JSP count JSP Monitor
jspReloadCount   ${domain}:type=​JspMonitor,name=jsp,WebModule=​*,J2EEApplication=​*,J2EEServer=​* On The number of JSP reloads JSP Monitor
Global Request Processor Availability   ${domain}:type=​GlobalRequestProcessor,name=* On Availability of the Global Request Processor Global Request Processor
bytesSent   ${domain}:type=​GlobalRequestProcessor,name=* Off Number of bytes sent by the request processor Global Request Processor
bytesReceived   ${domain}:type=​GlobalRequestProcessor,name=* Off Number of bytes received by the request processor Global Request Processor
errorCount   ${domain}:type=​GlobalRequestProcessor,name=* On Number of errors that occurred in the request processor Global Request Processor
processingTime   ${domain}:type=​GlobalRequestProcessor,name=* On Time the request processor has spent processing data Global Request Processor
requestCount   ${domain}:type=​GlobalRequestProcessor,name=* On Number of requests processed Global Request Processor
Cache Availability  

Tc Runtime 7.0.x: ${domain}:type=​Cache,host=*,context=*

Tc Runtime 8.0.x: ${domain}:type=​Cache,host=*,context=*

On Availability of the Cache mbean Cache
accessCount  

Tc Runtime 7.0.x: ${domain}:type=​Cache,host=*,context=*

Tc Runtime 8.0.x: ${domain}:type=​Cache,host=*,context=*

On Number of times the cache was accessed Cache
cacheMaxSize KB

Tc Runtime 7.0.x: ${domain}:type=​Cache,host=*,context=*

Tc Runtime 8.0.x: ${domain}:type=​Cache,host=*,context=*

Off Maximum size of the cache Cache
cacheSize KB

Tc Runtime 7.0.x: ${domain}:type=​Cache,host=*,context=*

Tc Runtime 8.0.x: ${domain}:type=​Cache,host=*,context=*

Off Current size of the cache Cache
desiredEntryAccessRatio  

Tc Runtime 7.0.x: ${domain}:type=​Cache,host=*,context=*

Tc Runtime 8.0.x: ${domain}:type=​Cache,host=*,context=*

Off The ratio of hits/misses of the cache Cache
hitsCount  

Tc Runtime 7.0.x: ${domain}:type=​Cache,host=*,context=*

Tc Runtime 8.0.x: ${domain}:type=​Cache,host=*,context=*

Off The number of hits for the cache Cache
maxAllocateIterations  

Tc Runtime 7.0.x: ${domain}:type=​Cache,host=*,context=*

Tc Runtime 8.0.x: ${domain}:type=​Cache,host=*,context=*

Off Maximum allowed number of removals during a make space action Cache
spareNotFoundEntries  

Tc Runtime 7.0.x: ${domain}:type=​Cache,host=*,context=*

Tc Runtime 8.0.x: ${domain}:type=​Cache,host=*,context=*

Off The spare amount of not found entries Cache