Analyzing Report Contents

8 Analyzing Report Contents

Oracle Coherence includes many predefined reports. Developers and system administrators use the reports to monitor and analyze operational statistics and troubleshoot potential problems.

An additional set of predefined reports are provided for Oracle Coherence*Web. The Coherence*Web reports are not discussed in this chapter. See Running Performance Reports in Administering HTTP Session Management with Oracle Coherence*Web.

This chapter includes the following sections:

Understanding the Cache Size Report
The cache size report indicates the size of a cache based on the number and size of the objects in the cache.
Understanding the Cache Storage Report
The cache storage report provides detailed metrics including index, querying, and eviction details for a cache.
Understanding the Cache Usage Report
The cache usage report provides information about cache usage (gets, puts, evictions, and so on).
Understanding the Executor Report
The executor report provides information about the running executors for a cluster.
Understanding the Federation Destination Report
The federation destination report indicates out-going replication statistics from the perspective of a federation participant who receives replicated data.
Understanding the Federation Origin Report
The federation origin report indicates in-coming replication statistics from the perspective of a federation participant who sends replicated data.
Understanding the Federation Status Report
The cache size report indicates the status for a federation participant.
Understanding the Flash Journal Report
The flash journal report displays statistics to help determine how well data is being stored to flash memory.
Understanding the JCache Configuration Report
The JCache configuration report shows what configuration options have been set on a JCache cache.
Understanding the JCache Statistics Report
The JCache statistic report contains information that is used to evaluate how well a JCache cache is performing.
Understanding the Management Report
The management report contains refresh statistics to help determine if the management framework is providing a timely view of management data for all MBeans.
Understanding the Memory Status Report
The memory status report contains statistics to help understand memory consumption on each member and across the grid.
Understanding the Network Health Detail Report
The network health detail report contains member-level details to help determine the health of network communications.
Understanding the Network Health Report
The network health report contains the primary aggregates to help determine the health of the network communications.
Understanding the Node List Report
The node list report provides information to help identify a cluster member.
Understanding the Persistence Detail Report
The persistence report provides detailed information about how cache persistence is performing for a particular service and node.
Understanding the Persistence Report
The persistence report provides information about how cache persistence is performing for a particular service.
Understanding the Proxy Report
The proxy report provides information about proxy servers and the information being transferred to clients.
Understanding the Proxy Connections Report
The proxy connections report provides information about the client connections for proxy servers in a cluster.
Understanding the Proxy HTTP Report
The proxy HTTP report provides information about HTTP acceptors that are configured on a proxy server.
Understanding the Ram Journal Report
The ram journal report displays statistics that are used to determine how well data is being stored to RAM memory.
Understanding the Service Report
The service report provides information for monitoring the health and performance of a service.
Understanding the Service Partitions Report
The service partitions report provides detailed metrics, including partition count, average and maximum partition sizes, and average and maximum storage sizes for a service.
Understanding the Topic Report
The Topic report provides detailed metrics for Topics defined within a cluster.
Understanding the Topic Subscribers Report
The Topic Subscribers report provides detailed metrics for Topic Subscribers defined within a cluster.
Understanding the Topic Subscriber Groups Report
The Topic Subscriber Groups report provides detailed metrics for Topic Subscriber Groups defined within a cluster.
Understanding the Transaction Manager Report
The transaction manager report provides detailed transaction manager statics from all transaction service instances in a cluster.
Understanding the View Report
The view report provides information about the views defined for a cluster.

Understanding the Cache Size Report

The cache size report indicates the size of a cache based on the number and size of the objects in the cache. The size does not include backup copies, indexes, or overhead. The size is reported for caches that set the <unit-calculator> subelement of <local-scheme> to BINARY. The name of the cache size report is timestamp-cache-size.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-cache-size.txt represents a cache size report for January 31, 2009 at 1:00 a.m.

Table 8-1 describes the contents of a cache size report.

Table 8-1 Contents of the Cache Size Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Service`	`String`	The name of the cache service.
`Cache Name`	`String`	The name of the cache.
`CacheSize`	`Double`	The number of objects in the cache.
`MemoryBytes`	`Double`	The number of bytes consumed by the objects in the cache.
`MemoryMB`	`Double`	The number of Megabytes (MB) consumed by the objects in the cache.
`Avg Object Size`	`Double`	The average amount of memory consumed by each object.

Parent topic: Analyzing Report Contents

Understanding the Cache Storage Report

The cache storage report provides detailed metrics including index, querying, and eviction details for a cache. The name of the executor report is timestamp-report-cache-storage.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-report-proxy-connections.txt represents an executor report for January 31, 2009 at 1:00 a.m.

Note:

This report is not included in report-group.xml but is available by running report-all.xml.

Table 8-2 describes the contents of the cache storage report.

Table 8-2 Contents of the Cache Storage Report

Attribute	Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Date`	`Date`	A timestamp for each report refresh.
`Service`	`String`	The service name.
`Cache`	`String`	The cache name.
`NodeId`	`String`	The numeric member identifier.
`Query Contention Count`	`Long`	The total number of times a query had to be re-evaluated due to a concurrent update since the last report refresh. This statistic provides a measure of the impact of concurrent updates on query performance. If the total number of queries is Q and the number of contentions is C, then the expected performance degradation factor should be no more than (Q + C)/Q.
`Eviction Count`	`Long`	The total number of evictions for the cache across the cluster since the last report refresh.
`Insert Count`	`Long`	The number of inserts into the backing map since the last report refresh. In addition to standard inserts that are caused by put and invoke operations or synthetic inserts that are caused by get operations with read-through backing map topology, this counter increments when distribution transfers move resources into the underlying backing map and decrements when distribution transfers move the data out.
`Remove Count`	`Long`	The number of removes from the backing map since the last report refresh. Removes are caused by operations such as clear, remove, or invoke.
`Optimized Query Count`	`Long`	The total number of queries that were fully resolved using indexes since the last report refresh.
`Optimized Query Total Millis`	`Long`	The total execution time, in milliseconds, for queries that were fully resolved using indexes since the last report refresh.
`Non-optimized Query Count`	`Long`	The total number of parallel queries that could not be resolved (or that were partially resolved) using indexes since the last report refresh.
`Non-optimized Query Total Millis`	`Long`	The total execution time, in milliseconds, for queries that could not be resolved (or that were partially resolved) using indexes since the last report refresh.
`Indexing Total Millis`	`Long`	The cumulative duration, in milliseconds, of index builds since the last report refresh.
`Index Total Units`	`Long`	The total units used by all indices on the associated cache.
`Max Query Threshold Millis`	`Long`	The query statistics threshold, defining when a query has been running long enough to be interesting for recording.
`Max Query Duration Millis`	`Long`	The duration, in milliseconds, of the longest query execution since statistics were last reset.
`MaxQuery Description`	`String`	A string representation of a query with the longest execution time exceeding the `MaxQuery Threshold Millis` attribute's value since statistics were last reset.
`Optimized Query Average Millis`	`Long`	The average execution time, in milliseconds, for queries that were fully resolved using indexes since statistics were last reset.
`Non-optimized Query Average Millis`	`Long`	The average execution time, in milliseconds, for queries that could not be resolved (or that were partially resolved) using indexes since statistics were last reset.
`Locks Granted`	`Long`	The number of locks currently granted for the portion of the partitioned cache managed by `StorageManager`.
`Locks Pending`	`Long`	The number of pending lock requests for the portion of the partitioned cache managed by the `StorageManager`.
`Listener Key Count`	`Long`	The number of key-based listeners registered with the `StorageManager`.
`Listener Filter Count`	`Long`	The number of filter-based listeners registered with the `StorageManager`.
`Listener Registration Count`	`Long`	The number of listener registrations since the last report refresh.

Parent topic: Analyzing Report Contents

Understanding the Cache Usage Report

The cache usage report provides information about cache usage (gets, puts, evictions, and so on). The name of the cache usage report is timestamp-cache-usage.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2010013113-cache-usage.txt represents a cache usage report for January 31, 2010 at 1:00 p.m.

Table 8-3 describes the contents of the cache usage report.

Table 8-3 Contents of the Cache Usage Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts, and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Time`	`Date`	A timestamp for each report refresh.
`Service`	`String`	The name of the cache service.
`Cache Name`	`String`	The name of the cache.
`Tier`	`String`	Whether the cache resides in the front tier (local cache) or back tier (remote cache). The value is either `front` or `back`.
`Total Puts`	`Double`	The total number of puts for the cache across the cluster since the last report refresh.
`Total Puts Millis`	`Double`	The total number of milliseconds spent on `put()` invocation across the cluster since the last report refresh.
`Total Gets`	`Double`	The total number of gets for the cache across the cluster since the last report refresh.
`Total Gets Millis`	`Double`	The total number of milliseconds spent on `get()` invocation across the cluster since the last report refresh.
`Total Hits`	`Double`	The total number of visits for the cache across the cluster since the last report refresh.
`Total Hits Millis`	`Double`	The total number of milliseconds spent on `get()` invocation that is a hit across the cluster since the last report refresh.
`Total Misses`	`Double`	The total number of misses for the cache across the cluster since the last report refresh.
`Total Misses Millis`	`Double`	The total number of milliseconds spent on `get()` invocation that is a miss across the cluster since the last report refresh.
`Total Writes`	`Double`	The total number of storage writes for the cache across the cluster since the last report refresh.
`Total Write Millis`	`Double`	The total number of milliseconds spent in storage write operations across the cluster since the last report refresh.
`Total Reads`	`Double`	The total number of reads from a cache store for the cache across the cluster since the last report refresh.
`Total Read Millis`	`Double`	The total number of milliseconds spent on cache store reads for the cache across the cluster since the last time the report executed.
`Total Failures`	`Long`	The total number of failures for the cache across the cluster since the last report refresh.
`Total Queue`	`Long`	The sum of the queue link sizes across the cluster.
`Evictions`	`Long`	The total number of evictions for the cache across the cluster since the last report refresh.
`Cache Prunes`	`Long`	The total number of prunes for the cache across the cluster since the last report refresh.
`Cache Prunes Millis`	`Long`	The total number of milliseconds spent in the prune operation across the cluster since the last report refresh.

Parent topic: Analyzing Report Contents

Understanding the Executor Report

The executor report provides information about the running executors for a cluster.The name of the executor report is timestamp-executors.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-executors.txt represents an executor report for January 31, 2009 at 1:00 a.m.

Table 8-4 describes the contents of the executor report.

Table 8-4 Contents of the Executor Report

Attribute	Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`ReportData`	`Date`	A timestamp for each report refresh.
`Name`	`String`	The logical name of the executor.
`Id`	`String`	The unique ID of this executor.
`MemberId`	`Long`	The location where the executor is running.
`State`	`String`	The state of the executor.
`Description`	`String`	The description of this executor. The following options are available: JOINING - Indicates that the executor is joining the orchestration. RUNNING - Indicates that the executor is accepting and executing the tasks. CLOSING_GRACEFULLY - Indicates that the executor has commenced graceful closing. No new tasks will be accepted, but existing ones will run to completion. CLOSING - Indicates that the executor has commenced closing. CLOSED - Indicates that the executor is closed. REJECTING - Indicates that the executor is rejecting tasks.
`TaksInProgressCount`	`Integer`	The in progress task count.
`TasksCompleted`	`Integer`	The completed tasks count for the time period.
`TasksRejectedCount`	`Integer`	The rejected tasks count for the time period.

Parent topic: Analyzing Report Contents

Understanding the Federation Destination Report

The federation destination report indicates out-going replication statistics from the perspective of a federation participant who receives replicated data. The name of the federation destination report is timestamp-federation-destination.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-federation-destination.txt represents a report for January 31, 2009 at 1:00 a.m.

Table 8-5 describes the contents of a federation destination report.

Table 8-5 Contents of the Federation Destination Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts, and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Time`	`Date`	A timestamp for each report refresh.
`Node ID`	`Long`	The member for the federation statistics.
`Name`	`String`	The name of the sender.
`State`	`String`	The state of the participant. For example: `INITIAL`, `IDLE`, `CONNECTING`, `STOPPED`, `PAUSED`, `ERROR`, or `YIELDING`
`Status`	`Integer`	The status of the participant. One of the following: `0` – Ok `1` – Warning `2` – Error
`CurrentBandwidth`	`Double`	The current utilized bandwidth in Megabits per second for sending replicate message.
`TotalBytesSent`	`Long`	The total number of bytes that were sent.
`TotalEntriesSent`	`Long`	The total number of cache entries that were sent.
`TotalRecordsSent`	`Long`	The total number of journal records that were sent. A journal record can consist of multiple cache entries that are part of the same transaction.
`TotalMsgSent`	`Long`	The total number of replication messages that were sent. A replication message can contain multiple journal records.
`TotalMsgUnacked`	`Long`	The total number of un-acknowledged replication messages.
`RecordBacklogDelayTimePercentileMillis`	`Long`	The 90-percentile value of the time (in milliseconds) the journal records are in the cache waiting to be replicated.
`MsgNetworkRoundTripTimePercentileMillis`	`Long`	The 90-percentile value of the round trip time (in milliseconds) taken for the transmission of replication messages, application of changes on the destination cluster, and the receipt of the corresponding acknowledgment messages over the network.
`MsgApplyTimePercentileMillis`	`Long`	The 90-percentile value of the time (in milliseconds) it took to apply the replication messages on the destination.
`BytesSent/sec`	`Long`	The bytes sent per second.
`MsgsSent/sec`	`Long`	The messages sent per second.
`MaxBandwidth`	`Double`	The maximum bandwidth in megabits per second for sending replicate messages. A value of `-1.0` means the maximum bandwidth is not configured.
`ErrorDescription`	`String`	An error description. A value is only returned if the sender is in an `ERROR` state.
`SendTimeoutMillis`	`Long`	The send timeout that is configured for the participant.
`GeoIp`	`String`	The location metadata that is configured for the participant.
`ReplicateAllPercentComplete`	`Long`	The percent of work completed for a `replicateAll` request.
`ReplicateAllTotalTime`	`Long`	The total time (in milliseconds) the `replicateAll` request took.
`ReplicateAllPartitionCount`	`Integer`	The total number of partitions in the `replicateAll` request.
`ReplicateAllPartitionCompletedCount`	`Integer`	The total number of partitions completed for the `replicateAll` request.
`ReplicateAllPartitionErrorCount`	`Integer`	The number of partitions with error responses for the`replicateAll` request. Check `ReplicateAllLastException` in the DestinationMBean for details of the last exception and the log for details of all the errors.

Parent topic: Analyzing Report Contents

Understanding the Federation Origin Report

The federation origin report indicates in-coming replication statistics from the perspective of a federation participant who sends replicated data. The name of the federation origin report is timestamp-federation-origin.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-federation-origin.txt represents a report for January 31, 2009 at 1:00 a.m.

Table 8-6 describes the contents of a federation origin report.

Table 8-6 Contents of the Federation Origin Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts, and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Time`	`Date`	A timestamp for each report refresh.
`Node ID`	`Long`	The member for the federation statistics.
`TotalBytesReceived`	`Long`	The total number of bytes that were received.
`TotalRecordsReceived`	`Long`	The total number of journal records that were received. A journal record could consist of multiple cache entries that are part of the same transaction.
`TotalEntriesReceived`	`Long`	The total number of cache entries that were received.
`TotalMsgReceived`	`Long`	The total number of replication messages that were received. A replication message could contain multiple journal records.
`TotalMsgUnacked`	`Long`	The total number of un-acknowledged replication messages.
`MsgApplyTimePercentileMillis`	`Long`	The 90-percentile value of the time (in milliseconds) it took to apply the replication messages on the destination.
`RecordBacklogDelayTimePercentileMillis`	`Long`	The 90-percentile value of the time (in milliseconds) the journal records are in the cache waiting to be replicated.
`BytesReceived/sec`	`Long`	The bytes received per second.
`MsgsReceived/sec`	`Long`	The messages received per second.
`TotalErrorRequests`	`Integer`	The total number of `ReplicateMessage` requests with error. Check the log for details of the errors.

Parent topic: Analyzing Report Contents

Understanding the Federation Status Report

The cache size report indicates the status for a federation participant. The name of the federation status report is timestamp-federation-status.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-federation-status.txt represents a cache size report for January 31, 2009 at 1:00 a.m.

Table 8-7 describes the contents of a federation status report.

Table 8-7 Contents of the Federation Status Report

Column	Data Type	Description
`Node ID`	`Long`	The member for the federation statistics.
`Name`	`String`	The name of the sender.
`State`	`String`	The state of the participant. One of: `INITIAL` `IDLE` `READY` `SENDING` `CONNECTING` `CONNECT_WAIT` `STOPPED` `PAUSED` `ERROR` `YIELDING` `BACKLOG_EXCESSIVE` `BACKLOG_NORMAL` `DISCONNECTED`
`Error Description`	`String`	An error description. A value is only returned if the sender is in an `ERROR` state.

Parent topic: Analyzing Report Contents

Understanding the Flash Journal Report

The flash journal report displays statistics to help determine how well data is being stored to flash memory. The name of the flash journal report is timestamp-flashjournal.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2010013113-flashjournal.txt represents a flash journal report for January 31, 2010 at 1:00 p.m.

Table 8-8 describes the contents of the flash journal report.

Table 8-8 Contents of the Flash Journal Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Time`	`Date`	A timestamp for each report refresh.
`Node ID`	`Long`	The member for the flash journal statistics.
`FileCount`	`Integer`	The number of journal files that are currently in use.
`BinaryStoreCount`	`Integer`	The number of active `JournalBinaryStore` objects that are using this journal.
`TotalDataSize`	`Long`	The amount of data, in bytes, that is currently stored for this journal.
`TotalFileSize`	`Long`	The total size of all journal files for this journal.
`BacklogCount`	`Integer`	The number of serialized values that have yet to be stored in the journal.
`BacklogSize`	`Integer`	The maximum size, in bytes, of the backlog. The backlog is the amount of serialized values that have yet to be stored in the journal. Client threads are blocked if this limit is exceeded and remain blocked until the backlog recedes below this limit.
`PoolSize`	`Integer`	The total size, in bytes, of all available buffers in the pool.

Parent topic: Analyzing Report Contents

Understanding the JCache Configuration Report

The JCache configuration report shows what configuration options have been set on a JCache cache. JCache caches are configured programmatically using the JCache API when the cache is created. The name of the report is timestamp-jcache-configuration.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013113-jcache-configuration.txt represents a management report for January 31, 2009 at 1:00 p.m.

Table 8-9 describes the contents of the JCache configuration report.

Table 8-9 Contents of the JCache Configuration Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`ReportTime`	`Date`	A timestamp for each report refresh.
`CacheManager`	`String`	The JCache `CacheManager` instance that created the cache. Coherence cache managers are scoped and uniquely identified by a cache configuration file that defines a `JCacheNamespace` handler class.
`Cache`	`String`	The name of the cache.
`KeyType`	`String`	The required key type for the cache.
`ValueType`	`String`	The required value type for the cache.
`ManagementEnabled`	`Boolean`	Specifies whether management is enabled for the cache.
`StatisticsEnabled`	`Boolean`	Specifies whether performance statistics are being collected for the cache.
`ReadThrough`	`Boolean`	Specifies whether the cache operates in read-through mode.
`WriteThrough`	`Boolean`	Specifies whether the cache operates in write-through mode.
`StoreByValue`	`Boolean`	Specifies whether the cache uses store-by-value or store by-reference semantics. A value of `true` indicates that keys and values are stored by value. A value of `false` indicates that keys and values are stored by reference.

Parent topic: Analyzing Report Contents

Understanding the JCache Statistics Report

The JCache statistic report contains information that is used to evaluate how well a JCache cache is performing. The name of the report is timestamp-jcache-statistics.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013113-jcache-statistics.txt represents a management report for January 31, 2009 at 1:00 p.m.

Table 8-10 describes the contents of the JCache statistics report.

Table 8-10 Contents of the JCache Statistics Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`ReportTime`	`Date`	A timestamp for each report refresh.
`CacheManager`	`String`	The JCache `CacheManager` instance that created the cache. Coherence cache managers are scoped and uniquely identified by a cache configuration file that defines a `JCacheNamespace` handler class.
`Cache`	`String`	The name of the cache
`CacheGets`	`Long`	The total number of `get` operations. The value is equal to the sum of hits and misses and does not include operations that check for the existence of a key.
`CachePuts`	`Long`	The total number of put operations including operations that replace and existing entry.
`CacheRemovals`	`Long`	The total number of `remove` operations. The value does not include evictions initiated by the cache to free up space.
`CacheHits`	`Long`	The number of successful `get` operations.
`CacheMisses`	`Long`	The number of unsuccessful `get` operations.
`CacheEvictions`	`Long`	The total number of evictions from the cache. An eviction is initiated by the cache to free up space. An eviction is not considered a `remove` operation. Note: This attribute is not implemented by the Coherence JCache provider.
`AverageGetTime`	`Float`	The average time to perform `get` operations. For read-through caches, the time does not include the time that is required to load entries because of a cache miss.
`AveragePutTime`	`Float`	The average time to perform `put` operations.
`AverageRemoveTime`	`Float`	The average time to perform `remove` operations.
`CacheHitPercentage`	`Float`	The percentage of cache requests that return an entry. The percentage is reported as a decimal value and is calculated using the value of cache hits divided by cache `get` operations.
`CacheMissPercentage`	`Float`	The percentage of cache requests that do not return an entry. The percentage is reported as a decimal value and is calculated using the value of cache misses divided by cache `get` operations.

Parent topic: Analyzing Report Contents

Understanding the Management Report

The management report contains refresh statistics to help determine if the management framework is providing a timely view of management data for all MBeans. The name of the management report is timestamp-management.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013113-Management.txt represents a management report for January 31, 2009 at 1:00 p.m.

Table 8-11 describes the contents of the management report.

Table 8-11 Contents of the Management Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`ReportTime`	`Date`	A timestamp for each report refresh.
`RefreshPolicy`	`String`	The refresh policy that is currently set. The policy determines how to refresh data for remote models.
`RefreshTime`	`Date`	The timestamp when this model was last retrieved from a corresponding member. For local servers it is the local time.
`RefreshExcessCount`	`Long`	The number of times that the MBean server predictively refreshed information and the information was not accessed.
`RefreshCount`	`Long`	The total number of snapshots retrieved since the statistics were last reset.
`RefreshPredictionCount`	`Long`	The number of times that the MBean server used a predictive algorithm to refresh MBean information.
`RefreshTimeoutCount`	`Long`	The number of times that this management member has timed out while attempting to refresh remote MBean attributes.

Parent topic: Analyzing Report Contents

Understanding the Memory Status Report

The memory status report contains statistics to help understand memory consumption on each member and across the grid. A memory status report must be run as part of a report group. The memory status report relies on platform MBean information. See Filtering MBeans. The name of the memory status report is timestamp-memory-status.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013115-memory-status.txt represents a memory status report for January 31, 2009 at 3:00 p.m.

Table 8-12 describes the contents of the memory status report.

Table 8-12 Contents of the Memory Status Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Time`	`Date`	A timestamp for each report refresh.
`JVM Uptime`	`Long`	The amount of time since the last JVM start.
`Node Id`	`Long`	The member for the memory statistics.
`Gc Name`	`String`	The name of the garbage collector.
`CollectionCount`	`Long`	The number of garbage collections since the last JVM start.
`Delta Collection Count`	`Long`	The number of garbage collections since the last report refresh.
`CollectTime`	`Long`	The number of milliseconds that the JVM has spent on garbage collection since the start of the JVM.
`Delta Collect Time`	`Long`	The number of milliseconds that the JVM has spent on garbage collection since the last report refresh.
`Last GC Start Time`	`Long`	The start time of the last garbage collection.
`Last GC Duration Millis`	`Long`	The total amount of time of the last garbage collection.
`Last GC Stop Time`	`Long`	The stop time of the last garbage collection.
`Heap Committed`	`Long`	The number of heap bytes committed at the time the report ran.
`Heap Init`	`Long`	The number of heap bytes initialized at the time the report ran.
`Heap Max`	`Long`	The maximum number of bytes used by the JVM since its start.
`Heap Used`	`Long`	The bytes used by the JVM at the time the report ran.
`HeapCommittedMB`	`Long`	The heap in megabytes committed at the time the report ran.
`HeapInitMB`	`Long`	The heap in megabytes initialized at the time the report ran.
`HeapMaxMB`	`Long`	The maximum number of megabytes used by the JVM since its start.
`HeapUsedMB`	`Long`	The heap in megabytes used by the JVM at the time the report ran.

Parent topic: Analyzing Report Contents

Understanding the Network Health Detail Report

The network health detail report contains member-level details to help determine the health of network communications. The name of the network health detail report is timestamp-network-health-detail.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013114-network-health-detail.txt represents a network health detail report for January 31, 2009 at 2:00 p.m.

Table 8-13 describes the contents of the network health detail report.

Table 8-13 Contents of the Network Health Detail Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Time`	`Date`	A timestamp for each report refresh.
`RefreshTime`	`Date`	The system time when management information was last retrieved from a corresponding node. Local servers display the local time.
`Node Id`	`Long`	The member for the network statistics.
`Tx Success`	`Double`	The publisher success rate for the member. If this value is within 2% to 3% of the `Min Node Tx Success` and more than 10% less than the `Grid Tx Success` for the batch in the Network Health File (see Table 8-14), the corresponding member may be having difficulty communicating with the cluster. A poor success rate can occur due to a constrained CPU, constrained network bandwidth, or high network latency.
`Rx Success`	`Double`	The receiver success rate for the member. If this value is within 2% to 3% of the `Min Node Rx Success` and more than 10% less than the `Grid Rx Success` for the batch in the Network Health File (see Table 8-14), the corresponding member may be having difficulty communicating with the cluster. A poor success rate can occur due to a constrained CPU, constrained network bandwidth, or high network latency.
`PacketsSent`	`Double`	The total number of network packets sent by the member.
`Current Packets Sent`	`Long`	The number of packets sent by the member since the last report refresh.
`PacketsResent`	`Long`	The total number of network packets re-sent by the member. Packets are re-sent when the receiver of the packet receives an invalid packet or when an acknowledge packet is not sent within the appropriate amount of time.
`Current Packet Resent`	`Long`	The number of network packets re-sent by the member since the last report refresh.
`PacketsRepeated`	`Long`	The total number of packets received multiple times.
`Current Repeated`	`Long`	The number of packets received multiple times since the last report refresh.
`Packets Received`	`Long`	The total number of packets received by the member.
`Current Packets Received`	`Long`	The total number of packets received by the member since the last report refresh.
`TransportSentMessages`	`Long`	The number of messages sent by the service-dedicated transport since the last report refresh.
`TransportReceivedMessages`	`Long`	The number of messages received by the service-dedicated transport since the last report refresh.
`TransportBacklogDelay`	`Long`	The total number of milliseconds that the requests were delayed due to draining the backlog since the last report refresh.

Parent topic: Analyzing Report Contents

Understanding the Network Health Report

The network health report contains the primary aggregates to help determine the health of the network communications. The name of the network health report is timestamp-network-health.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013113-network-health.txt represents a network health report for January 31, 2009 at 1:00 p.m.

Table 8-14 describes the contents of the network health report.

Table 8-14 Contents of the Network Health Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Time`	`Date`	A timestamp for each report refresh.
`Min Node Rx Success`	`Double`	The minimum receiver success rate for a member in the cluster. If this value is considerably less (10%) than the `Grid Rx Success` rate, analyze the network health detail report.
`Grid Rx Success`	`Double`	The receiver success rate for the grid as a whole. If this value is below 90%, analyze the network health detail report.
`Min Node Tx Success`	`Double`	The minimum publisher success rate for a member in the cluster. If this value is considerably less (10%) than the `Grid Rx Success` rate, analyze the network health detail report.
`Grid TX Success`	`Double`	The publisher success rate for the grid as a whole. If this value is below 90%, analyze the network health detail report.

Parent topic: Analyzing Report Contents

Understanding the Node List Report

The node list report provides information to help identify a cluster member. Due to the transient nature of the node identifier (nodeId), the reporter logs out a list of members and user-defined member identity information. See member-identity in Developing Applications with Oracle Coherence. The name of the nodes list report is timestamp-nodes.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-nodes.txt represents a node list report for January 31, 2009 at 1:00 a.m.

Table 8-15 describes the contents of the node list report.

Table 8-15 Contents of the Node List Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Time`	`Date`	A timestamp for each report refresh.
`RefreshTime`	`Date/Time`	The time at which the information was refreshed from a remote member. If the time is different than the refresh time on other rows in the batch, the member did not respond in a timely matter. This is often caused by a member performing a garbage collection. Any information regarding a member with an old refresh date is questionable.
`Node Id`	`String`	The numeric member identifier.
`UnicastAddress`	`String`	The Unicast address for the member.
`MemberName`	`String`	The member name.
`ProcessName`	`String`	The process name for the member.
`RoleName`	`String`	The role name for the member.
`MachineName`	`String`	The computer name for the member.
`RackName`	`String`	The rack name for the member.
`SiteName`	`String`	The site name for the member.

Parent topic: Analyzing Report Contents

Understanding the Persistence Detail Report

The persistence report provides detailed information about how cache persistence is performing for a particular service and node. The name of the persistence detail report is timestamp-persistence-detail.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-persistence-detail.txt represents a persistence detail report for January 31, 2009 at 1:00 a.m.

Table 8-16 describes the contents of the persistence detail report.

Table 8-16 Contents of the Persistence Detail Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`ReportTime`	`Date`	A timestamp for each report refresh.
`Service`	`String`	The name of the partitioned cache service.
`PersistenceMode`	`String`	The current persistence mode for this service: `active` – all mutating cache operations are persisted using the configured persistence environment. `on-demand` – a persistence environment has been configured and is available but is not being actively used. n/a – persistence is not configured for this service.
`NodeId`	`Long`	The member for the persistence statistics.
`PersistenceLatencyAverage`	`Float`	The average latency (in milliseconds) added to a mutating cache operation by active persistence operations.
`PersistenceLatencyMax`	`Long`	The maximum latency (in milliseconds) added to a mutating cache operation by an active persistence operation.
`PersistenceActiveSpaceUsed`	`Long`	The amount of space (in bytes) that is used by active persistence.
`PersistenceActiveSpaceTotal`	`Long`	The total size (in bytes) of the file system for use by active persistence.
`PersistenceActiveSpaceAvailable`	`Long`	The remaining space (in bytes) available on the file system for active persistence.
`PersistenceSnapshotSpaceTotal`	`Long`	The total size (in bytes) of the file system to store snapshots.
`PersistenceSnapshotSpaceAvailable`	`Long`	The remaining space (in bytes) available on the file system to store snapshots.
`PersistenceBackupSpaceUsed`	`Long`	The total size (in bytes) used by the persistence layer to persist backup cache data.
`PersistenceBackupSpaceTotal`	`Long`	The total size (in bytes) of the file system used by the persistence layer to persist backup cache data.
`PersistenceBackupSpaceAvailable`	`Long`	The total remaining free space (in bytes) of the file system used by the persistence layer to persist backup cache data.

Parent topic: Analyzing Report Contents

Understanding the Persistence Report

The persistence report provides information about how cache persistence is performing for a particular service. The name of the persistence report is timestamp-persistence.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-persistence.txt represents a persistence report for January 31, 2009 at 1:00 a.m.

Table 8-17 describes the contents of the persistence report.

Table 8-17 Contents of the Persistence Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`ReportTime`	`Date`	A timestamp for each report refresh.
`Service`	`String`	The name of the partitioned cache service.
`PersistenceMode`	`String`	The current persistence mode for this service: `active` – all mutating cache operations are persisted using the configured persistence environment. `on-demand` – a persistence environment has been configured and is available but is not being actively used. `n/a` – persistence is not configured for this service.
`PersistenceTotalActiveSpaceUsed`	`Long`	The amount of space (in bytes) that is used by active persistence
`PersistenceLatencyAverageAcrossNodes`	`Float`	The average latency for all nodes (in milliseconds) added to a mutating cache operation by active persistence operations.
`PersistenceLatencyMaxAcrossNodes`	`Long`	The maximum latency for all nodes (in milliseconds) added to a mutating cache operation by an active persistence operation.
`PersistenceBackupSpaceUsed`	`Long`	The total size (in bytes) used by the persistence layer to persist backup cache data.

Parent topic: Analyzing Report Contents

Understanding the Proxy Report

The proxy report provides information about proxy servers and the information being transferred to clients. The name of the proxy report is timestamp-network-report-proxy.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-report-proxy.txt represents a proxy report for January 31, 2009 at 1:00 a.m.

Table 8-18 describes the contents of the proxy report.

Table 8-18 Contents of the Proxy Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Time`	`Date`	A timestamp for each report refresh.
`RefreshTime`	`Date/Time`	The timestamp when this model was last retrieved from a corresponding member. For local servers it is the local time.
`Service Name`	`String`	The name of the proxy service.
`HostIp`	`String`	The IP Address and Port of the proxy service.
`NodeId`	`String`	The numeric member identifier.
`ConnectionCount`	`Long`	The current number of connections to the proxy service.
`OutgoingByteBacklog`	`Long`	The number of bytes queued to be sent by the proxy service.
`OutgoingMessageBacklog`	`Long`	The number of messages queued by the proxy service.
`Bytes Sent`	`Long`	The number of bytes sent by the proxy service since the last report refresh.
`Bytes Received`	`Long`	The number of bytes received by the proxy service since the last report refresh.
`Messages Sent`	`Long`	The number of messages sent by the proxy service since the last report refresh.
`Messages Received`	`Long`	The number of messages received by the proxy service since the last report refresh.

Parent topic: Analyzing Report Contents

Understanding the Proxy Connections Report

The proxy connections report provides information about the client connections for proxy servers in a cluster. The name of the proxy connections report is timestamp-report-proxy-connections.txt, where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-report-proxy-connections.txt represents a proxy connections report for January 31, 2009 at 1:00 a.m.

Table 8-19 describes the contents of the proxy connections report.

Table 8-19 Contents of the Proxy Connections Report

Attribute	Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`ReportDate`	`Date`	The timestamp for each report refresh.
`ServiceName`	`String`	The service name of the proxy server.
`NodeId`	`String`	The numeric member identifier.
`UUID`	`Integer`	The unique ID of this client connection.
`RemoteAddress`	`String`	The remote address of the client.
`RemotePort`	`Integer`	The remote port of the client.
`ClientAddress`	`String`	The client address of the client (may be different from the `RemoteAddress` depending upon the load balancer configuration).
`ClientProcessName`	`String`	The name or process id of the client.
`ClientRole`	`String`	The role of the client.
`ConnectionTimeMillis`	`Long`	The time in milliseconds that the client has been connected.
`OutgoingByteBacklog`	`Long`	The number of bytes queued to be sent to the client.
`OutgoingMessageBacklog`	`Long`	The number of messages queued to be sent to the client.
`BytesSent`	`Long`	The number of bytes sent to the client since the last report refresh.
`BytesReceived`	`Long`	The number of bytes received from the client since the last report refresh.
`MessagesSent`	`Long`	The number of messages sent to the client since the last report refresh.
`MessagesReceived`	`Long`	The number of messages received from the client since the last report refresh.
`Member`	`String`	The string representation of the client.

Parent topic: Analyzing Report Contents

Understanding the Proxy HTTP Report

The proxy HTTP report provides information about HTTP acceptors that are configured on a proxy server. The name of the proxy report is timestamp-report-proxy-http.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-report-proxy-http.txt represents a proxy report for January 31, 2009 at 1:00 a.m.

Table 8-20 describes the contents of the proxy HTTP report.

Table 8-20 Contents of the Proxy HTTP Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Time`	`Date`	A timestamp for each report refresh.
`RefreshTime`	`Date/Time`	The timestamp when this model was last retrieved from a corresponding member. For local servers it is the local time.
`Service Name`	`String`	The name of the proxy service.
`HTTPServerType`	`String`	The type of HTTP server or `n/a` if the HTTP protocol is not used.
`HostIp`	`String`	The IP Address and Port of the proxy service.
`NodeId`	`String`	The numeric member identifier.
`AverageRequestSize`	`Float`	The average size of the HTTP requests.
`AverageResponseSize`	`Float`	The average size of the HTTP responses.
`AverageRequestTime`	`Float`	The average processing time in milliseconds for HTTP requests.
`TotalErrorCount`	`Long`	The number of HTTP requests that caused errors.
`TotalRequestCount`	`Long`	The number of requests since the HTTP server was started or the statistics were reset.
`ResponseCount1xx`	`Long`	The number of HTTP responses in the 100-199 range.
`ResponseCount2xx`	`Long`	The number of HTTP responses in the 200-299 range.
`ResponseCount3xx`	`Long`	The number of HTTP responses in the 300-399 range.
`ResponseCount4xx`	`Long`	The number of HTTP responses in the 400-499 range.
`ResponseCount5xx`	`Long`	The number of HTTP responses in the 500-599 range.

Parent topic: Analyzing Report Contents

Understanding the Ram Journal Report

The ram journal report displays statistics that are used to determine how well data is being stored to RAM memory. The name of the ram journal report is timestamp-ramjournal.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2010013113-ramjournal.txt represents a ram journal report for January 31, 2010 at 1:00 p.m.

Table 8-21 describes the contents of the ram journal report.

Table 8-21 Contents of the Ram Journal Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Time`	`Date`	A timestamp for each report refresh.
`Node Id`	`Long`	The member for the RAM journal statistics.
`FileCount`	`Integer`	The number of journal files that are currently in use.
`BinaryStoreCount`	`Integer`	The number of active `JournalBinaryStore` objects that are using this journal.
`TotalDataSize`	`Long`	The amount of data, in bytes, that is currently stored for this journal.
`TotalFileSize`	`Long`	The total size of all journal files for this journal.

Parent topic: Analyzing Report Contents

Understanding the Service Report

The service report provides information for monitoring the health and performance of a service. The Request Count and Task Count values help to determine the performance and throughput of the service. The RequestPendingCount and Task Backlog values help to identify capacity issues or blocked processes. The Task Hung Count, Task Timeout Count, Thread Abandoned Count, and Request Timeout Count values represent the number of unsuccessful executions that have occurred in the system. The name of the service report is timestamp-service.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2010013113-service.txt represents a service report for January 31, 2010 at 1:00 p.m.

Table 8-22 describes the contents of the service report.

Table 8-22 Contents of the Service Report

Column	Data Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Time`	`Date`	A timestamp for each report refresh.
`Service`	`String`	The service name.
`Node Id`	`String`	The numeric member identifier.
`RefreshTime`	`Date`	The system time when the service information was updated from a remote member.
`Request Count`	`Long`	The number of requests since the last report refresh execution.
`RequestPendingCount`	`Long`	The number of pending requests at the time of the report.
`RequestPendingDuration`	`Long`	The duration for the pending requests at the time of the report.
`Request Timeout Count`	`Long`	The number of request timeouts since the last report refresh.
`Task Count`	`Long`	The number of tasks executed since the last report refresh.
`TaskBacklog`	`Long`	The task backlog at the time of the report.
`Task Timeout Count`	`Long`	The number of task timeouts since the last report refresh.
`Task Hung Count`	`Long`	The number of tasks that hung since the last report refresh.
`Thread Abandoned Count`	`Long`	The number of threads abandoned since the last report refresh.
`Owned Partitions Primary`	`Integer`	The number of partitions that this member owns (responsible for the primary storage).
`Owned Partitions Backups`	`Integer`	The number of partitions that this member backs up (responsible for the backup storage).
`Partitions Endangered`	`Integer`	The total number of partitions that are not currently backed up.
`Partitions Vulnerable`	`Integer`	The total number of partitions that are backed up on the same machine where the primary partition owner resides.
`Partitions Unbalanced`	`Integer`	The total number of primary and backup partitions that remain to be transferred until the partition distribution across the storage enabled service members is fully balanced.
`Outgoing Partition Count`	`Integer`	The number of partitions that are currently being transferred by this service member to other members.
`Thread Count`	`Integer`	The number of threads in the service thread pool. To configure a thread count, set the `thread-count-min` and `thread-count-max` elements to the same value.
`Thread Idle Count`	`Integer`	The number of currently idle threads in the service thread pool.
`Thread Utilization %`	`Double`	The percentage of threads in the pool that are being used. The percentage is calculated based on the thread count and the number of threads that are idle.

Parent topic: Analyzing Report Contents

Understanding the Service Partitions Report

The service partitions report provides detailed metrics, including partition count, average and maximum partition sizes, and average and maximum storage sizes for a service. The name of the service partitions report is timestamp-service-partitions.txt, where timestamp is in the YYYYMMDDHH format. For example, a file named 2009013101-service-partitions.txt represents an executor report for January 31, 2009 at 1:00 a.m.

Note:

This report is not included in report-group.xml but is available by running report-all.xml.

Table 8-23 describes the contents of the service partitions report.

Table 8-23 Contents of the Service Partitions Report

Attribute	Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Date`	`Date`	A time stamp for each report refresh.
`Service`	`String`	The name of the service.
`Partition Count`	`Integer`	The configured number of partitions for the service.
`Backup Count`	`Integer`	The configured number of partition backups to be maintained by the service.
`Fair Share Primary`	`Integer`	The number of primary partitions per storage-enabled service member that a strategy attempts to maintain.
`Fair Share Backup`	`Integer`	The number of backup partitions per storage-enabled service member that a strategy currently attempts to maintain.
`Service Node Count`	`Integer`	The number of storage-enabled nodes running the service.
`Service Machine Count`	`Integer`	The number of machines that host storage-enabled nodes running the service.
`Service Rack Count`	`Integer`	The number of racks that host storage-enabled nodes running the service.
`Service Site Count`	`Integer`	The number of sites that host storage-enabled nodes running this service.
`Strategy Name`	`String`	The name of the partition assignment strategy that is in use.
`HA Status`	`String`	The high availability status for the service. The valid values are: `MACHINE-SAFE`: The loss of a machine will not result in data loss. `RACK-SAFE`: The loss of a rack will not result in data loss. `SITE-SAFE`: The loss of a site will not result in data loss. `NODE-SAFE`: A cluster node can be stopped without any data loss. `ENDANGERED`: Abnormal termination of a cluster node that runs the service can cause data loss. Note: To achieve `RACK-SAFE` and `SITE-SAFE`, each cluster node must have its rack and site name configured.
`HA Target`	`String`	The high availability status that the strategy attempts to achieve. Valid values are the same as the `HAStatus` attribute.
`Remaining Distribution Count`	`Integer`	The number of partition transfers that remain to be completed before the service achieves the goals set by the strategy.
`Average Partition Size KB`	`Integer`	The average partition storage size in kilobytes.
`Max Partition Size KB`	`Integer`	The maximum partition storage size in kilobytes.
`Average Storage Size KB`	`Integer`	The average node storage size in kilobytes.
`Max Storage Size KB`	`Integer`	The maximum node storage size in kilobytes.
`Max Load Node Id`	`Integer`	The node identified with the maximum node storage size.

Parent topic: Analyzing Report Contents

Understanding the Topic Report

The Topic report provides detailed metrics for Topics defined within a cluster. The name of the Topic report is timestamp-topic.txt where the timestamp is in the YYYYMMDDHH format. For example, a file named 2009013101-topics.txt represents a Topic report for January 31, 2009 at 1:00 a.m.

Note:

This report is not included in report-group.xml but is available by running report-all.xml.

Table 8-24 describes the contents of the Topic report.

Table 8-24 Contents of the Topic Report

Attribute	Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Date`	`Date`	A time stamp for each report refresh.
`Service`	`String`	The name of the service.
`Name`	`String`	The name of the Topic.
`NodeId`	`String`	The numeric member identifier.
`ChannelCount`	`Integer`	The number of channels in the Topic.
`PublishedCount`	`Long`	The number of published messages since the last report refresh.
`PublishedFifteenMinuteRate`	`Double`	The rate of publishing messages over the last 15 minutes.
`PublishedFiveMinuteRate`	`Double`	The rate of publishing messages over the last five minutes.
`PublishedOneMinuteRate`	`Double`	The rate of publishing messages over the last one minute.
`PublishedMeanRate`	`Double`	The mean rate at which messages are published.

Parent topic: Analyzing Report Contents

Understanding the Topic Subscribers Report

The Topic Subscribers report provides detailed metrics for Topic Subscribers defined within a cluster. The name of the Topic Subscribers report is timestamp-topic-subscribers.txt where the timestamp is in the YYYYMMDDHH format. For example, a file named 2009013101-topic-subscribers.txt represents a Topic Subscribers report for January 31, 2009 at 1:00 a.m.

Note:

This report is not included in report-group.xml but is available by running report-all.xml.

Table 8-25 describes the contents of the Topic Subscribers report.

Table 8-25 Contents of the Topic Subscribers Report

Attribute	Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Date`	`Date`	A time stamp for each report refresh.
`Service`	`String`	The name of the service.
`Name`	`String`	The name of the Topic.
`SubscriberGroup`	`String`	The subscriber group to which the subscriber belongs.
`Id`	`Long`	The Id of the subscriber.
`NodeId`	`String`	The numeric member identifier.
`Backlog`	`Long`	The number of outstanding receive requests.
`ChannelAllocations`	`String`	The subscriber's allocated channels.
`ChannelCount`	`Integer`	The number of channels in the Topic.
`Disconnections`	`Long`	The number of times the subscriber has disconnected since the last report refresh.
`Notifications`	`Long`	The number of channel notifications received since the last report refresh.
`Polls`	`Long`	The total number of polls for messages since the last report refresh.
`ReceiveCompletionsCount`	`Long`	The number completed receive requests since the last report refresh.
`ReceiveCompletionsFifteenMinuteRate`	`Double`	The rate at which receive requests are completed over the last 15 minutes.
`ReceiveCompletionsFiveMinuteRate`	`Double`	The rate at which receive requests are completed over the last five minutes.
`ReceiveCompletionsOneMinuteRate`	`Double`	The rate at which receive requests are completed over the last one minute.
`ReceiveCompletionsMeanRate`	`Double`	The mean rate at which receive requests are completed.
`ReceiveEmpty`	`Long`	The number of empty receive requests since the last report refresh.
`ReceiveErrors`	`Long`	The number of exceptionally completed receive requests since the last report refresh.
`ReceivedCount`	`Long`	The number of elements received since the last report refresh.
`State`	`Integer`	The state of the subscriber. Valid values are: 0 - Initial 1 - Connected 2 - Disconnected 3 - Closing 4 - Closed
`StateName`	`String`	The state of the subscriber as a string.
`Waits`	`Long`	The number of elements received since the last report refresh.

Parent topic: Analyzing Report Contents

Understanding the Topic Subscriber Groups Report

The Topic Subscriber Groups report provides detailed metrics for Topic Subscriber Groups defined within a cluster. The name of the Topic Subscriber Groups report is timestamp-topic-subscriber-groups.txt where the timestamp is in the YYYYMMDDHH format. For example, a file named 2009013101-topic-subscriber-groups.txt represents a Topic Subscriber Groups report for January 31, 2009 at 1:00 a.m.

Note:

This report is not included in report-group.xml but is available by running report-all.xml.

Table 8-26 describes the contents of the Topic Subscriber Groups report.

Table 8-26 Contents of the Topic Subscriber Groups Report

Attribute	Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Date`	`Date`	A time stamp for each report refresh.
`Service`	`String`	The name of the service.
`Topic`	`String`	The name of the Topic.
`Name`	`String`	The name of the subscriber group.
`NodeId`	`String`	The numeric member identifier.
`ChannelCount`	`Integer`	The number of channels in the Topic.
`PolledCount`	`Long`	The total number of polled messages since the last report refresh.
`PolledFifteenMinuteRate`	`Double`	The rate at which messages are polled over the last 15 minutes.
`PolledFiveMinuteRate`	`Double`	The rate at which messages are polled over the last five minutes.
`PolledOneMinuteRate`	`Double`	The rate at which messages are polled over the last one minute.
`PolledMeanRate`	`Double`	The mean rate at which messages are polled.

Parent topic: Analyzing Report Contents

Understanding the Transaction Manager Report

The transaction manager report provides detailed transaction manager statics from all transaction service instances in a cluster. The name of the transaction manager report is timestamp-report-transaction.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-report-transaction.txt represents a transaction report for January 31, 2009 at 1:00 a.m.

Table 8-27 describes the contents of the transaction manager report.

Table 8-27 Contents of the Transaction Manager Report

Attribute	Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`Report Date`	`Date`	A timestamp for each report refresh.
`Service`	`String`	The name of the service.
`NodeId`	`String`	The numeric member identifier.
`TotalActive`	`Long`	The total number of currently active transactions. An active transaction is counted as any transaction that contains at least one modified entry and is yet to be committed or rolled back. The coordinator member for this transaction maintains the count even though multiple members may have participated in the transaction.
`TimeoutMillis`	`Long`	The transaction timeout value in milliseconds. This value applies only to transactional connections obtained after the value is set. This attribute is currently not supported.
`CommittedCount`	`Long`	The total number of transactions that have been committed by the transaction manager for the time period. The coordinator member for this transaction maintains the count even though multiple members may have participated in the transaction.
`RecoveredCount`	`Long`	The total number of transactions that have been recovered by the transaction manager for the time period. The coordinator member for this transaction maintains the count even though multiple members may have participated in the transaction.
`RolledbackCount`	`Long`	The total number of transactions that have been rolled back by the transaction manager for the time period. The coordinator member for this transaction maintains the count even though multiple members may have participated in the transaction.
`TransactionMillis`	`Long`	The cumulative time (in milliseconds) that was spent on active transactions for the time period.

Parent topic: Analyzing Report Contents

Understanding the View Report

The view report provides information about the views defined for a cluster.The name of the view report is timestamp-view-usage.txt where the timestamp is in YYYYMMDDHH format. For example, a file named 2009013101-view-usage.txt represents a view report for January 31, 2009 at 1:00 a.m.

Table 8-28 describes the contents of the view report.

Table 8-28 Contents of the View Report

ViewMBean Attribute	Type	Description
`Batch Counter`	`Long`	A sequential counter to help integrate information between related files. This value resets when the reporter restarts and is not consistent across members. However, it is helpful when trying to integrate files.
`ReportData`	`Date`	A timestamp for each report refresh.
`Service`	`String`	The service to which the view cache belongs.
`NodeId`	`String`	The numeric member identifier.
`Name`	`String`	The name of the view cache.
`Size`	`Long`	The number of entries in the view-cache.

Parent topic: Analyzing Report Contents