You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the release of Cassandra 4.1, we have noticed a regression in the metric collection process for the collectd_mcac_micros_bucket_ metric, which is essential for monitoring and performance analysis. The MCAC module is no longer generating this metric as expected.
Steps to Reproduce:
Use Cassandra version 4.1+.
curl http://localhost:9103/metrics | grep micros_
Expected Behavior:
The collectd_mcac_micros_bucket_ metric should be generated and updated as before in Cassandra 4.1, allowing proper monitoring.
Environment:
Cassandra Version: 4.1.0
MCAC version : 0.3.4
The text was updated successfully, but these errors were encountered:
Just for adding information, this issue is still present with more recent Cassandra 4.1 (tested 4.1.5) and the MCAC 0.3.4-beta1
I captured the following error in the Cassandra 4.1 logs which looks like it's falling in the ballpark of the issue:
INFO [insights-6-1] 2024-09-17 15:15:32,037 NoSpamLogger.java:105 - Not able to get buckets for org.apache.cassandra.metrics.dropped_message.internal_dropped_latency.finalize_propose_msg 128 type org.apache.cassandra.metrics.DecayingEstimatedHistogramReservoir$EstimatedHistogramReservoirSnapshot
Description:
With the release of Cassandra 4.1, we have noticed a regression in the metric collection process for the collectd_mcac_micros_bucket_ metric, which is essential for monitoring and performance analysis. The MCAC module is no longer generating this metric as expected.
Steps to Reproduce:
Expected Behavior:
The collectd_mcac_micros_bucket_ metric should be generated and updated as before in Cassandra 4.1, allowing proper monitoring.
Environment:
The text was updated successfully, but these errors were encountered: