[
https://issues.apache.org/jira/browse/CASSANDRA-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727825#action_12727825
]
Eric Evans edited comment on CASSANDRA-272 at 7/6/09 3:52 PM:
--------------------------------------------------------------
After some discussion on IRC between myself, Sammy, and Jonathan, it was
decided that a) we'll go without a TableMBean unless/until there something
Table-specific to expose, and b) we need a CFSMbean organization that is human
readable in tools like jconsole. One possible way is by manipulating the object
name to parent by the table name instead of the CF name.
was (Author: urandom):
After some discussion on IRC between myself, Sammy, and Jonathan, it was
decided that a) we'll go without a TableMBean unless/until there something
Table-specific to expose, and b) we need a CFSMbean organization that is human
readable as well, possibly by manipulating the object name to parent by
tablename instead of CF name.
> 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
>
>
> 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.
