[ https://issues.apache.org/jira/browse/AMBARI-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmytro Sen updated AMBARI-15766: -------------------------------- Status: Patch Available (was: Open) > 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)