cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sammy Yu (JIRA)" <>
Subject [jira] Issue Comment Edited: (CASSANDRA-272) Enhance how metrics are exposed
Date Mon, 06 Jul 2009 06:01:16 GMT


Sammy Yu edited comment on CASSANDRA-272 at 7/5/09 11:00 PM:

0002 is self-contained patch (ignore 0001 patch):
   * Registers the mbean properly to use domain, type, and key-value pairs
   * Adds write latency and operation metric to super column family mbean
   * All table metric calculation is calculated at the super column level
   * Adds a new nodeprobe stat command which retrieves these metrics

      was (Author: sammy.yu):
    Self-contained patch, ignore previous 0001 patch.
> Enhance how metrics are exposed
> -------------------------------
>                 Key: CASSANDRA-272
>                 URL:
>             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
> 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.

View raw message