[
https://issues.apache.org/jira/browse/AMBARI-15766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235863#comment-15235863
]
Hudson commented on AMBARI-15766:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4633 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4633/])
AMBARI-15766 Create a new alert type that is based on timeseries metrics (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3691090923d141ea57a8d13931692d0e4b441f37])
* ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/alerts.json
* ambari-agent/src/test/python/ambari_agent/TestAlertSchedulerHandler.py
*
ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionFactory.java
*
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py
* ambari-common/src/main/python/ambari_commons/firewall.py
* ambari-agent/src/test/python/ambari_agent/TestAlerts.py
* ambari-common/src/main/python/ambari_commons/urllib_handlers.py
* ambari-agent/src/main/python/ambari_agent/alerts/metric_alert.py
*
ambari-server/src/main/java/org/apache/ambari/server/state/alert/SourceType.java
* ambari-agent/src/test/python/ambari_agent/TestAmsAlert.py
*
ambari-server/src/main/java/org/apache/ambari/server/state/alert/MetricSource.java
* ambari-agent/src/main/python/ambari_agent/alerts/ams_alert.py
* ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py
* ambari-common/src/main/python/ambari_commons/aggregate_functions.py
*
ambari-server/src/main/java/org/apache/ambari/server/state/alert/AmsSource.java
> 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)
