cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan King (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2751) Improved Metrics collection
Date Fri, 10 Jun 2011 00:45:58 GMT

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

Ryan King updated CASSANDRA-2751:
---------------------------------

    Description: 
Collecting metrics in cassandra needs to be easier. Currently the amount of work required
to expose one new metric in the server and consume it outside the server is way to high.

In my mind, collecting a new metric in the server should be a single line of code and consuming
it should be easily doable from any programming language.

There are several options for better metrics collection on the JVM:

https://github.com/twitter/ostrich
https://github.com/codahale/metrics/
https://github.com/twitter/commons/tree/master/src/java/com/twitter/common/stats

We should look at these

  was:
Collecting metrics in cassandra needs to be easier. Currently the amount of work required
to expose one new metric in the server and consume it outside the server is way to high.

In my mind, collecting a new metric in the server should be a single line of code and consuming
it should be easily doable from any programming language.

There are several options for better metrics collection on the JVM:

https://github.com/twitter/ostrich
https://github.com/codahale/metrics/

We should look at these


> Improved Metrics collection
> ---------------------------
>
>                 Key: CASSANDRA-2751
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2751
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Ryan King
>            Assignee: Ryan King
>
> Collecting metrics in cassandra needs to be easier. Currently the amount of work required
to expose one new metric in the server and consume it outside the server is way to high.
> In my mind, collecting a new metric in the server should be a single line of code and
consuming it should be easily doable from any programming language.
> There are several options for better metrics collection on the JVM:
> https://github.com/twitter/ostrich
> https://github.com/codahale/metrics/
> https://github.com/twitter/commons/tree/master/src/java/com/twitter/common/stats
> We should look at these

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message