Package org.apache.cassandra.metrics
package org.apache.cassandra.metrics
-
ClassDescriptionMetrics related to AutoRepair.AutoRepair metrics manager holding all the auto-repair related metrics.Metrics for
ICache.Metrics for tracking information about CAS write requests.Makes integrating 3.0 metrics API with 2.0.A value class encapsulating a metric's owning class and name.Metrics forICache.Captures metrics of CIDR authorizerAdds ability to reset a histogramMetrics to track the size of incoming and outgoing bytes at Cassandra server.Metrics for tracking information about range requests.Metrics for tracking information about write requests.Metrics for commit logMetrics for compaction.A decaying histogram reservoir where values collected during each minute will be twice as significant as the values collected in the previous minute.MetricNameFactory that generates default MetricName of metrics.Metrics for dropped messages by verb.Find the most frequent sample.Metrics forHintsService.Metrics forHintsService.Metrics for internode connections.Metrics for internode connections.Metrics forColumnFamilyStore.Metrics about latenciesMaxSampler<T>Note:Sampler.samplerExecutoris single threaded but we still need to synchronize as we have access from both internal and the external JMX context that can cause races.Metrics for messagesMetrics related to Read Repair.A meter metric which measures mean throughput as well as fifteen-minute and two-hour exponentially-weighted moving average throughputs.Sampler<T>Represents the ranked items collected during a sample periodA reservoir that scales the values before updating.Scale the input value.Metrics related to Storage.Metrics for streaming.Metrics forColumnFamilyStore.Metrics forThreadPoolExecutor.Tracks top partitions, currently by size and by tombstone count Collects during full and preview (-vd) repair since then we read the full partition Note that since we can run sub range repair there might be windows where the top partitions are not correct - for example, assume we track the top 2 partitions for this node: tokens with size: (a, 100); (b, 40); (c, 10); (d, 100); (e, 50); (f, 10) - top2: a, d now a is deleted and we run a repair for keys [a, c] - top2: b, d and when we repair [d, f] - top2: d, e