ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Siddharth Wagle <>
Subject [ANNOUNCE] Merging branch for Ambari Metrics System to trunk
Date Mon, 01 Dec 2014 23:04:49 GMT
Hi devs,

I am planning to merge branch-metrics-dev to current trunk in the next 24

The patch is up for review at AMBARI-5707
<>. A set of instructions
on how to build and test the Metrics System should be available shortly on
the Jira.


On Mon, Sep 22, 2014 at 10:45 AM, Siddharth Wagle <>

> Hi all devs,
> Creating a branch from trunk, to commit some of the working prototype
> implementation of Ambari metrics system as a starting point for this
> project. This is a feature branch and please do not commit any other code
> in it.
> Best Regards,
> Sid
> On Wed, Sep 17, 2014 at 10:01 AM, Siddharth Wagle <>
> wrote:
>> Please review the Jira AMBARI-5707
>> <>. "Replace Ganglia
>> with high performant and pluggable Metrics System".
>> This Epic address issues with current metrics system with proposed
>> architecture for a new home grown Ambari metrics system with some of the
>> notable use cases highlighted below:
>> - Ability to horizontally scale out the metrics system
>> - SQL support to extend analytic capabilities on top of collected metrics
>> - Provide time-based as well as across host aggregation capabilities
>> - Ability to tee data to an external metrics system to store fine grained
>> data forever.
>> Please feel free to provide feedback.
>> Expect to see sub-topics / issues posted to this Epic with design docs.
>> Contributions welcome.
>> Best Regards,
>> Sid

NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message