Return-Path: X-Original-To: apmail-ambari-issues-archive@minotaur.apache.org Delivered-To: apmail-ambari-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D3B0F19B68 for ; Mon, 11 Apr 2016 17:47:25 +0000 (UTC) Received: (qmail 38639 invoked by uid 500); 11 Apr 2016 17:47:25 -0000 Delivered-To: apmail-ambari-issues-archive@ambari.apache.org Received: (qmail 38538 invoked by uid 500); 11 Apr 2016 17:47:25 -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 38514 invoked by uid 99); 11 Apr 2016 17:47:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Apr 2016 17:47:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 93C672C1F5D for ; Mon, 11 Apr 2016 17:47:25 +0000 (UTC) Date: Mon, 11 Apr 2016 17:47:25 +0000 (UTC) From: "Dmytro Sen (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-15766) Create a new alert type that is based on timeseries metrics MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-15766: -------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.2 > Create a new alert type that is based on timeseries metrics > ----------------------------------------------------------- > > Key: AMBARI-15766 > URL: https://issues.apache.org/jira/browse/AMBARI-15766 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-metrics > Affects Versions: 2.4.0 > Reporter: Dmytro Sen > Assignee: Dmytro Sen > Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15766-trunk_1.patch > > > There are a few requirements around creating alerts based on the time-series data stored in AMS. They fall in the the general category of: > identify a metrics (name of the metrics, app name) > - identify a window (e.g. last 10 minutes, last 1 day) > - get the data points > - add them up, or > - compute average, or > - compute standard deviations, or > ... > - compare the value to a threshold > - emit an alert if needed (WARN, CRITICAL, etc) > We should also allow for alerts based on multiple metrics but there is no ask for such a capability. Just something to keep in mind while designing. > It seems general enough that we should define an alert type that can be instantiated by services to define specific alerts. Users can add additional alerts if they so choose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)