ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-5707) Replace Ganglia with high performant and pluggable Metrics System
Date Thu, 23 Oct 2014 23:09:33 GMT

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

Siddharth Wagle updated AMBARI-5707:
------------------------------------
    Description: 
*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

!https://issues.apache.org/jira/secure/attachment/12669212/Revised%20archtecture%20diagram.png|width=800px!

  was:
*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




> 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: Epic
>          Components: ambari-agent, ambari-server
>    Affects Versions: 1.6.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>            Priority: Critical
>         Attachments: MetricsArchLatest.png, Revised archtecture diagram.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
> !https://issues.apache.org/jira/secure/attachment/12669212/Revised%20archtecture%20diagram.png|width=800px!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message