ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "subin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-5707) Replace Ganglia with high performant and pluggable Metrics System
Date Tue, 13 May 2014 03:01:21 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-5707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995984#comment-13995984
] 

subin commented on AMBARI-5707:
-------------------------------

+1 for this ,fantastic proposal .Something I had always wanted.
Considering the conflicting ganglia/nagios versions on existing customer setups.This would
help a lot.
Will this daemon be coded in python? I am suggesting something in C/scala/erlang (C best)
to capture data and dump it out as json.
And agent itself can also have a webui(disabled by default) which can show the metrics.
But OpenTSDB is already has python tcollector  and a LGPL .So would we be inspired from it
,and rewrite it ?
One last question I have is regarding whether you are considering to get the visualization
as good/similar as in ganglia
Ganglia uses RRDTool(i guess) which is again GPL. So does the plan also include improving
the server side to render the data in a different way.



> Replace Ganglia with high performant and pluggable Metrics System
> -----------------------------------------------------------------
>
>                 Key: AMBARI-5707
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5707
>             Project: Ambari
>          Issue Type: New Feature
>          Components: agent, controller
>    Affects Versions: 1.6.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>            Priority: Critical
>         Attachments: MetricsSystemArch.png
>
>
> Ambari Metrics System
> - Ability to collect metrics from Hadoop and other Stack services
> - Ability to retain metrics at a high precision for a configurable time period (say 5
days)
> - Ability to automatically purge metrics after retention period
> - At collection time, provide clear integration point for external system (such as TSDB)
> - At purge time, provide clear integration point for metrics retention by external system
> - Should provide default options for external metrics retention (say “HDFS”)
> - Provide tools / utilities for analyzing metrics in retention system (say “Hive schema,
Pig scripts, etc” that can be used with the default retention store “HDFS”)
> System Requirements
> - Must be portable and platform independent
> - Must not conflict with any existing metrics system (such as Ganglia)
> - Must not conflict with existing SNMP infra
> - Must not run as root
> - Must have HA story (no SPOF)
> Usage
> - Ability to obtain metrics from Ambari REST API (point in time and temporal)
> - Ability to view metric graphs in Ambari Web (currently, fixed)
> - Ability to configure custom metric graphs in Ambari Web (currently, we have metric
graphs “fixed” into the UI)
> - Need to improve metric graph “navigation” in Ambari Web (currently, metric graphs
do not allow navigation at arbitrary timeframes, but only at ganglia aggregation intervals)

> - Ability to “view cluster” at point in time (i.e. see all metrics at that point)
> - Ability to define metrics (and how + where to obtain) in Stack Definitions



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message