Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id F316E200C7E for ; Tue, 23 May 2017 22:49:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id F1BBB160BA4; Tue, 23 May 2017 20:49:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 2A8AF160BD3 for ; Tue, 23 May 2017 22:49:08 +0200 (CEST) Received: (qmail 64046 invoked by uid 500); 23 May 2017 20:49:07 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 63834 invoked by uid 99); 23 May 2017 20:49:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 May 2017 20:49:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id E4D231AFCC2 for ; Tue, 23 May 2017 20:49:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id H6gTOJ_xhiat for ; Tue, 23 May 2017 20:49:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id CA7BD60CC6 for ; Tue, 23 May 2017 20:49:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 43D7DE0DC9 for ; Tue, 23 May 2017 20:49:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9DEC42400B for ; Tue, 23 May 2017 20:49:04 +0000 (UTC) Date: Tue, 23 May 2017 20:49:04 +0000 (UTC) From: "Siddharth Wagle (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-21105) AMS: Anomaly Detection for specific metrics MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 23 May 2017 20:49:09 -0000 [ https://issues.apache.org/jira/browse/AMBARI-21105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21105: ------------------------------------- Issue Type: Epic (was: New Feature) > AMS: Anomaly Detection for specific metrics > ------------------------------------------- > > Key: AMBARI-21105 > URL: https://issues.apache.org/jira/browse/AMBARI-21105 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics > Affects Versions: 2.0.0 > Reporter: Siddharth Wagle > Assignee: Siddharth Wagle > Fix For: 3.0.0 > > > Metrics is one of the areas where we show the user a large amount of information, but it takes a lot of knowledge and understanding to make sense of what's good and bad about a metric value. Having the ability to detect anomalies in metrics will help set the stage for us to show to users only those metrics where we have concerns and we've decided that the change in metric values requires some attention. -- This message was sent by Atlassian JIRA (v6.3.15#6346)