1 Reply Latest reply on Jan 14, 2015 3:22 AM by Thomas Heute

    RHQ Metrics 0.2.6 - Released

    nstefan Newbie

      Hello Everybody,


      I am happy to announce release 0.2.6 of RHQ Metrics project.


      The artifacts can be downloaded from:

       

      Here is an overview of the features added in this release:

      • UI
        • Console uses new REST Api for new C* schema (and new capabilities)
      • Cassandra
        • Initial support for configuring data retention
          • per tenant
          • per metric
      • Embedded Cassandra
        • Packaged as EAR is now part of the distribution
        • "embedded_cass" argument starts the embedded storage server and allows the rest interface to use it
        • Default storage engine
        • Optimized for fast startup and low memory usage
        • Limited to single node deployment, cannot be clustered
        • NOTE: the memory engine is still part of the distribution, please see note below about that.
      • InfluxDB
        • Influx query parser based on ANTLR grammar replaces regular expression based parser (stronger base for full compatibility)
        • "limit" clause support
        • Post data on the Influx series endpoint
      • REST
        • More test coverage
        • Tests in the rest-tests module are now written in Groovy and the groovy-rest-tests module has been removed
        • Updated example docs
        • Removed deprecated 0.2.4 endpoints
      • start.sh
        • Script improved to allow just download of pre-build binaries
        • Added embedded Cassandra option

       

      NOTE: Memory Datastore

      0.2.6 release planning announced that the memory datastore will be dropped. After getting feedback on the proposal and testing with the embedded Cassandra we decided to reverse the decision. The primary reason is the unbeatable almost instant startup of the Memory Datastore. Although an embedded Cassandra takes just under 2 seconds to boot after the initial configuration, that does not beat the mere milliseconds required for the memory datastore. So we will support standalone Cassandra deployments (recommended), along with the volatile memory datastore and the new embedded single-node Cassandra deployment.

       

      A big "Thank you!" goes to John Sanda, Mike Thompson, Heiko Rupp, and Thomas Segismont for their project contributions.