Infinispan HotRod Connector Metrics: Difference between revisions
| Line 10: | Line 10: | ||
The counters can be used to calculate the read and write rate, in bytes/second. It is preferable to expose these metrics as a rate per second, as it gives an indication of the load on the node. Some monitoring solutions allow the rate to be calculated automatically (see [[DataDog_and_JMX#Counter|Data Dog counters]]). | The counters can be used to calculate the read and write rate, in bytes/second. It is preferable to expose these metrics as a rate per second, as it gives an indication of the load on the node. Some monitoring solutions allow the rate to be calculated automatically (see [[DataDog_and_JMX#Counter|Data Dog counters]]). | ||
{| | |||
| [[JDG_6_JMX#totalBytesRead|JDG 6 JMX]] | |||
|- | |||
| [[JDG 6 CLI#bytesRead|JDG 6 CLI]] | |||
|- | |||
| [[JDG 7 JMX#bytesRead|JDG 7 JMX]] | |||
|- | |||
| [[JDG 7 CLI#bytesRead|JDG 7 CLI]] | |||
|- | |||
|} | |||
=Number of Active Client Connections= | =Number of Active Client Connections= | ||
Revision as of 18:32, 25 October 2016
Internal
Bytes Read and Written
The HotRod connector exposes a cumulative counter for bytes read from the connector and bytes written to the connector. The metrics are exposed as longs.
The counters can be used to calculate the read and write rate, in bytes/second. It is preferable to expose these metrics as a rate per second, as it gives an indication of the load on the node. Some monitoring solutions allow the rate to be calculated automatically (see Data Dog counters).
| JDG 6 JMX |
| JDG 6 CLI |
| JDG 7 JMX |
| JDG 7 CLI |
Number of Active Client Connections
The HotRod connector reports the number of active client connections this node endpoint, as integer. It also reports the number of active client connections in the cluster. For the cluster-wide count, the node will make remote calls to aggregate results, so latency might have an impact on the speed of calculation of this attribute.
Worker Thread Count
The number of worker threads this connector was configured with, as integer. The value may be undefined, in which case it means the number of worker threads is the hardcoded default.