You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ryan King (JIRA)" <ji...@apache.org> on 2011/06/08 20:32:58 UTC
[jira] [Created] (CASSANDRA-2751) Improved Metrics collection
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/
We should look at these
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-2751) Improved Metrics collection
Posted by "Ryan King (JIRA)" <ji...@apache.org>.
[ 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