You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Zhe (Joe) Wang (JIRA)" <ji...@apache.org> on 2016/04/05 22:42:25 UTC
[jira] [Updated] (AMBARI-15720) AGGREGATE Alerts Should Not Expose
Repeat Tolerance or Tolerance Enabled Settings
[ https://issues.apache.org/jira/browse/AMBARI-15720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhe (Joe) Wang updated AMBARI-15720:
------------------------------------
Issue Type: Task (was: Bug)
> AGGREGATE Alerts Should Not Expose Repeat Tolerance or Tolerance Enabled Settings
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-15720
> URL: https://issues.apache.org/jira/browse/AMBARI-15720
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Zhe (Joe) Wang
> Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
>
> {{AGGREGATE}} type alerts should not expose a {{repeat_tolerance}} or {{repeat_tolerance_enabled}} setting in the web client. This is because of the nature of how {{AGGREGATE}} alerts functions. They respond to {{HARD}} alert events and are therefore simply a summary of the known alerts which have already reached their repeat tolerance levels.
> These types of alerts will not honor a global repeat tolerance value ({{cluster-env/alerts_repeat_tolerance}} nor will they honor changes to alert definitions of source type {{AGGREGATE}}.
> They effectively have a tolerance of 1 always.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)