You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jeremiah Jordan (JIRA)" <ji...@apache.org> on 2017/08/22 00:15:00 UTC

[jira] [Commented] (CASSANDRA-13642) Expose recent histograms in JmxHistograms

    [ https://issues.apache.org/jira/browse/CASSANDRA-13642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136069#comment-16136069 ] 

Jeremiah Jordan commented on CASSANDRA-13642:
---------------------------------------------

Looks good to me.  Definitely have written tools based on this behavior in the past.

> Expose recent histograms in JmxHistograms
> -----------------------------------------
>
>                 Key: CASSANDRA-13642
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13642
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability
>            Reporter: Chris Lohfink
>            Assignee: Chris Lohfink
>
> For monitoring tools that were written for the recent*Histograms the current decaying and all time values exposed by the JmxHistograms is not consumable. We can add a new attribute (easier with some tooling than operations to read) to expose it just like in storage service previously.
> Should additionally make it so this attribute only stores previous values if read, so that it does not add any additional memory cost to C* unless used since we already storing 2 versions of histogram for the decaying/alltime views.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org