Infinispan Monitoring: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(9 intermediate revisions by the same user not shown)
Line 6: Line 6:


* [[Infinispan Operations#Subjects|Infinispan Operations]]
* [[Infinispan Operations#Subjects|Infinispan Operations]]
* [[Infinispan Metrics Reference]]


=Relevance=
=Relevance=
Line 24: Line 23:


<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
:[[HotRod Client Metrics]]
:[[Infinispan_HotRod_Connector_Metrics|HotRod Connector Metrics]]
:[[Infinispan_HotRod_Connector_Metrics|HotRod Connector Metrics]]
:[[Infinispan Cache Metrics|Cache Metrics]]
:[[Infinispan Cache Metrics|Cache Metrics]]
:[[Infinispan Cache Manager Metrics|Cache Manager Metrics]]
</blockquote>
</blockquote>
<blockquote style="background-color: Tomato; border: solid thin red;">
:<br>Everything Below Must Be Reviewed<br><br>
</blockquote>
=TO REVIEW=
===Distributed Cache Statistics===
====cache-status====
A string describing the state of the cache. Example: "RUNNING"
The metric is also available as the "cacheStatus" JMX Attribute of the MBean
<pre>
jboss.infinispan:type=Cache,name="<cache-name>(dist_sync)",manager="clustered",component=Cache
</pre>
====clusterwide-number-of-entries====
See [[Infinispan Cache Number of Entries]].
====number-of-entries====
See [[Infinispan Cache Number of Entries]]
====clusterwide-hits====
A long representing the clustered number of cache attribute hits. May return null if the cache is not started. Also see <tt>[[#hits|hits]]</tt>.
====hits====
A long representing the number of cache attribute hits for a specific node. May return null if the cache is not started. Also see <tt>[[#clusterwide-hits|clusterwide-hits]]</tt>.
====misses====
A long representing the number of cache attribute misses for a specific node. May return null if the cache is not started. Also see <tt>[[#clusterwide-misses|clusterwide-misses]]</tt>.
====stores====
A long representing the number of put operations for this specific node. May return null if the cache is not started.  Also see <tt>[[#clusterwide-stores|clusterwide-stores]]</tt>.
====average-read-time====
A long representing the average time (in ms) a cache read operation, including hits and misses, requires to complete, for this specific node. May return null if the cache is not started.
The metric is also available as the "averageReadTime" JMX Attribute of the MBean
<pre>
jboss.infinispan:type=Cache,name="<cache-name>(dist_sync)",manager="clustered",component=Statistics
</pre>
====average-write-time====
A long representing the average time (in ms) a cache write operation requires to complete, for this specific node. May return null if the cache is not started.
The metric is also available as the "averageWriteTime" JMX Attribute of the MBean
<pre>
jboss.infinispan:type=Cache,name="<cache-name>(dist_sync)",manager="clustered",component=Statistics
</pre>
====average-replication-time====
A long representing the average time spent in the transport layer to duplicate data around the cluster, in milliseconds. Maintained by the RpcManager. Applies to both replicated and distributed caches.
The metric is also available as the "averageReplicationTime" JMX Attribute of the MBean
<pre>
jboss.infinispan:type=Cache,name="<cache-name>(dist_sync)",manager="clustered",component=RpcManager
</pre>
====replication-failures====
A long representing the number of data duplication failures. May return null if the cache is not started. Maintained by the RpcManager. Applies to both replicated and distributed caches.
The metric is also available as the "replicationFailures" JMX Attribute of the MBean
<pre>
jboss.infinispan:type=Cache,name="<cache-name>(dist_sync)",manager="clustered",component=RpcManager
</pre>
====success-ratio====
A percentage (double) representing successful duplications as a ratio of total duplications (successes/successes+failures). Maintained by the RpcManager. Applies to both replicated and distributed caches.
The metric is also available as the "successRatio" JMX Attribute of the MBean
<pre>
jboss.infinispan:type=Cache,name="<cache-name>(dist_sync)",manager="clustered",component=RpcManager
</pre>
====capacity-factor====
A read-write double that controls the proportion of entries that will reside on the local node, compared to the other nodes in the cluster. Value must be positive. This element is only used in 'distributed' cache instances. By default is undefined, which corresponds to a logical value of 1.0.
====clusterwide-hit-ratio====
A read-only double representing the cluster-wide hit/miss ratio for the cache (hits/hits+misses). May return null if the cache is not started. Also see <tt>[[#read-write-ratio|read-write-ratio]]</tt>.
====hit-ratio====
A double representing the hit/miss ratio for the this node (hits/hits+misses), where the number of successful attempts is divided by the total number of attempts. Expressed in percentage. May return null if the cache is not started. Also see <tt>[[#clusterwide-read-write-ratio|clusterwide-read-write-ratio]]</tt>.
====clusterwide-read-write-ratio====
A read-only double representing the cluster-wide read/write ratio of the cache ((hits+misses)/stores). May return null if the cache is not started.
====read-write-ratio====
A double representing the read/write ratio of the cache ((hits+misses)/stores) for this specific node. May return null if the cache is not started.
====clusterwide-remove-misses====
A read-only long representing the cluster-wide number of cache attribute remove misses. May return null if the cache is not started.
====clusterwide-remove-hits====
A read-only long representing the cluster-wide number of cache attribute remove hits. May return null if the cache is not started. Also see <tt>[[#remove-hits|remove-hits]]</tt>.
====remove-hits====
A long representing the number of cache attribute remove hits for the particular node in question. Also see <tt>[[#clusterwide-remove-hits|clusterwide-remove-hits]]</tt>.
====remove-misses====
A long representing the number of cache removal misses, where the removal was attempted but the key was not found. May return null if the cache is not started.
====activations====
A string representing the number of cache node activation events (bringing a node into memory from a cache store). May return null if the cache is not started.
For more details about cache activation see [[Infinispan_Concepts#Cache_Store_Activation|Cache Store Activation]].
====passivations====
A string representing the number of cache node passivation events (writing an entry from memory into a cache store). May return null if the cache is not started.
For more details about cache passivation see [[Infinispan_Concepts#Cache_Store_Passivation|Cache Store Passivation]].
====invalidations====
A string representing the number of cache invalidations. May return null if the cache is not started.
For more details about cache invalidation see [[Infinispan_Concepts#Invalidation_Mode|Invalidation Mode]].
====cache-loader-stores====
The number (as long) of cache loader store operations, for this specific node. May return null if the cache is not started.
====cache-loader-loads====
The number (as long) of cache loader load operations, for this specific node. May return null if the cache is not started.
====cache-loader-misses====
The long representing the cache loader miss operation, for this specific node. May return null if the cache is not started.
====prepares====
The long representing the number of transaction prepares, since the last reset. May return null if the cache is not started.
====commits====
The long representing the number of transaction commits, since the last reset. May return null if the cache is not started.
====rollbacks====
The long representing the number of transaction rollbacks, since the last reset. May return null if the cache is not started.
====number-of-locks-available====
An integer representing the number of exclusive locks available to this cache. Maintained by LockManager.
====Deprecated Attributes====
=====virtual-nodes=====

Latest revision as of 02:04, 28 October 2016

External

Internal

Relevance

  • JDG 6
  • JDG 7

Overview

This article describes choices of metrics for Infinispan production monitoring.


By default, Infinispan statistics are disabled, because enabling them may have a negative impact on the performance of the subsystem. Thus, statistics should be enabled only when required. For more details on how to enable statistics, see "Enabling Cache Statistics".

Metrics

HotRod Client Metrics
HotRod Connector Metrics
Cache Metrics
Cache Manager Metrics