6 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 Usage Report
  The cache usage report provides information about cache usage (gets, puts, evictions, and so on).
• 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 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.

6.1 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 6-1 describes the contents of a cache size report.

Table 6-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

6.2 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 6-2 describes the contents of the cache usage report.

Table 6-2 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

6.3 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 6-3 describes the contents of a federation destination report.

Table 6-3 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. One of: INITIAL, IDLE, READY, SENDING, CONNECTING, CONNECT_WAIT, STOPPED, PAUSED, ERROR, YIELDING, BACKLOG_EXCESSIVE, BACKLOG_NORMAL, DISCONNECTED
Status	Integer	The status of the participant. Statuses are: 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 time (in milliseconds) taken by transmission of replication messages and the corresponding acknowledge 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

6.4 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 6-4 describes the contents of a federation origin report.

Table 6-4 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

6.5 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 6-5 describes the contents of a federation status report.

Table 6-5 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.

6.6 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 6-6 describes the contents of the flash journal report.

Table 6-6 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

6.7 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 6-7 describes the contents of the JCache configuration report.

Table 6-7 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.

6.8 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 6-8 describes the contents of the JCache statistics report.

Table 6-8 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.

6.9 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 6-9 describes the contents of the management report.

Table 6-9 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

6.10 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 6-10 describes the contents of the memory status report.

Table 6-10 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

6.11 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 6-11 describes the contents of the network health detail report.

Table 6-11 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 6-12), 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 6-12), 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

6.12 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 6-12 describes the contents of the network health report.

Table 6-12 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.

6.13 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 6-13 describes the contents of the node list report.

Table 6-13 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

6.14 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 6-14 describes the contents of the persistence detail report.

Table 6-14 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

6.15 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 6-15 describes the contents of the persistence report.

Table 6-15 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.

6.16 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 6-16 describes the contents of the proxy report.

Table 6-16 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

6.17 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 6-17 describes the contents of the proxy HTTP report.

Table 6-17 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

6.18 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 6-18 describes the contents of the ram journal report.

Table 6-18 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

6.19 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 6-19 describes the contents of the service report.

Table 6-19 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