cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sammy Yu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-272) Enhance how metrics are exposed
Date Mon, 06 Jul 2009 23:59:14 GMT

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

Sammy Yu updated CASSANDRA-272:
-------------------------------

    Attachment: 0003-Work-for-CASSANDRA-272.patch

 * Removed TableMBean
 * Register CFMBean so that the name is the tablename and supercolumn key is the name of supercolumn.
 * Modified nodeprobe to calculate the table metrics



> Enhance how metrics are exposed
> -------------------------------
>
>                 Key: CASSANDRA-272
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-272
>             Project: Cassandra
>          Issue Type: New Feature
>    Affects Versions: 0.3
>            Reporter: Sammy Yu
>            Assignee: Sammy Yu
>            Priority: Minor
>             Fix For: 0.3
>
>         Attachments: 0001--Work-for-cassandra-272.patch, 0002--Work-for-cassandra-272.patch,
0003-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.


Mime
View raw message