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

Posted to commits@cassandra.apache.org by "Michael Greene (JIRA)" <ji...@apache.org> on 2009/08/11 23:32:15 UTC

[jira] Updated: (CASSANDRA-272) Enhance how metrics are exposed

     [ https://issues.apache.org/jira/browse/CASSANDRA-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Greene updated CASSANDRA-272:
-------------------------------------

    Component/s: Tools

> Enhance how metrics are exposed
> -------------------------------
>
>                 Key: CASSANDRA-272
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-272
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>    Affects Versions: 0.3
>            Reporter: Sammy Yu
>            Assignee: Sammy Yu
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: 0001--Work-for-cassandra-272.patch, 0002--Work-for-cassandra-272.patch, 0003-Work-for-CASSANDRA-272.patch, 0004-Work-for-CASSANDRA-272.patch
>
>
> Had discussion on IRC about the metric interfaces that are used in the code today.  There are two sets one using IAnalyticsSource to send data to Gangalia and another set of interface using JMX MBeans (ie, ColumnStoreFamily).  
> Since FB is not using Gangalia anymore and it looks like the other VMAnalyticsSource is already available via JMX, we should prefer to expose metrics through JMX.  I will add a new TableMBean which exposes the metrics in  DBAnalyticsSource.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.