Was this page helpful?
List of metrics¶
In this section you can find a description of each metric type used by the driver and a list of all metrics provided by the driver.
Metric types¶
Metric Type |
Description |
---|---|
Counter |
Counters are atomic |
Gauge |
A Gauge is simply an action that returns the instantaneous measure of a value, where the value abitrarily increases and decreases. |
Meter |
A Meter measures the rate at which an event occurs along with a total count of the occurances. |
Timer |
A Timer allows us to measure the duration of a type of event, the rate of its occurrence and provide duration statistics. |
Session level metrics¶
Name |
Type |
C# Property |
Description |
---|---|---|---|
|
Gauge |
|
The number of nodes to which the driver has at least one active connection. |
|
Counter |
|
The number of timeouts in synchronous API calls like |
|
Meter |
|
The number and rate of bytes received for the entire session. |
|
Meter |
|
The number and rate of bytes sent for the entire session. |
|
Timer |
|
The throughput and latency percentiles of CQL requests (overall duration of the |
Node level metrics¶
Name |
Type |
C# Property |
Description |
---|---|---|---|
|
Gauge |
|
The number of connections open to this node for regular requests. |
|
Gauge |
|
The number of requests currently executing on the connections to this node. |
|
Timer |
|
The throughput and latency percentiles of individual CQL messages sent to this node as part of an overall request. |
|
Meter |
|
The number and rate of bytes sent to this node. |
|
Meter |
|
The number and rate of bytes received from this node. |
|
Counter |
|
The number of speculative executions triggered by a slow response from this node. |
|
Counter |
|
The number of errors encountered while trying to establish a connection to this node. Authentication errors are tracked separately in |
|
Counter |
|
The number of authentication errors encountered while trying to establish a connection to this node. |
|
Counter |
|
The number of times this node replied with a |
|
Counter |
|
The number of times this node replied with a |
|
Counter |
|
The number of times this node replied with an |
|
Counter |
|
The number of times this node replied with a server error that doesn’t fall under other |
|
Counter |
|
The number of times a request was aborted before the driver even received a response from this node. Client timeouts are |
|
Counter |
|
The number of times the driver failed to send a request to this node. |
|
Counter |
|
The number of times the request failed due to a client-side timeout, when the client didn’t hear back from the server within |
|
Counter |
|
The number of read timeout errors on this node that caused the RetryPolicy to trigger a retry. |
|
Counter |
|
The number of write timeout errors on this node that caused the RetryPolicy to trigger a retry. |
|
Counter |
|
The number of unavailable errors on this node that caused the RetryPolicy to trigger a retry. |
|
Counter |
|
The number of errors other than read timeouts, write timeouts and unavailable errors on this node that caused the RetryPolicy to trigger a retry. |
|
Counter |
|
The total number of retries triggered by the RetryPolicy. |
|
Counter |
|
The number of read timeout errors on this node that were ignored by the RetryPolicy. |
|
Counter |
|
The number of write timeout errors on this node that were ignored by the RetryPolicy. |
|
Counter |
|
The number of unavailable errors on this node that were ignored by the RetryPolicy. |
|
Counter |
|
The number of errors other than read timeouts, write timeouts and unavailable errors on this node that were ignored by the RetryPolicy. |
|
Counter |
|
The total number of errors on this node that were ignored by the RetryPolicy. |