[
https://issues.apache.org/jira/browse/AMBARI-10144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370405#comment-14370405
]
Siddharth Wagle commented on AMBARI-10144:
------------------------------------------
Linking the parent Epic.
> Ambari Metrics System v0.2 - Enhancements
> -----------------------------------------
>
> Key: AMBARI-10144
> URL: https://issues.apache.org/jira/browse/AMBARI-10144
> Project: Ambari
> Issue Type: Epic
> Components: ambari-metrics
> Affects Versions: 2.1.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 2.1.0
>
>
> Epic used to track Jiras for Ambari-2.1.0
> *Requirements*:
> - At collection time, provide clear integration point for external system
> (such as TSDB) *(2.1)*
> - At purge time, provide clear integration point for metrics retention by
> external system *(2.1)*
> - Should provide default options for external metrics retention (say "HDFS")
> *(2.1)*
> - 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") *(2.1)*
> *System Requirements*
> - Must have HA story (no SPOF) *(2.1)*
> *Usage*
> - Ability to configure custom metric graphs in Ambari Web (currently, we have
> metric graphs "fixed" into the UI) *(2.2)* (!)
> - Need to improve metric graph "navigation" in Ambari Web (currently, metric
> graphs do not allow navigation at arbitrary timeframes, but only at
> aggregation intervals) *(2.1)*
> - Ability to "view cluster" at point in time (i.e. see all metrics at that
> point) *(2.1)*
> - Ability to define metrics (and how + where to obtain) in Stack Definitions
> *(2.1)*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
