[
https://issues.apache.org/jira/browse/AMBARI-8909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-8909.
-------------------------------------
Resolution: Fixed
> Alert Summary Counts Should Honor Maintenance States
> ----------------------------------------------------
>
> Key: AMBARI-8909
> URL: https://issues.apache.org/jira/browse/AMBARI-8909
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
>
> When an alert is put into maintenance mode, the backend will continue to
> represent with its actual state (OK, WARN, CRIT, etc) but will also indicate
> it is in maintenance mode so that clients can decide how to handle this
> scenario.
> However, this presents a problem when returning summary count information. If
> there are 10 alerts and 2 are CRITICAL, but 1 of them is in maintenance mode,
> the count information should represent 8 OK, 1 CRITICAL, 1 MAINTENANCE.
> Along those same lines, if a host has an alert in CRITICAL but that alert is
> in maintenance mode, then the host should not be reported as having a
> CRITICAL alert in the host count information.
> The summary structures should take into account maintenance mode markers so
> that web client badges don't show red when there are maintenance mode alerts
> that have been triggered.
> {code}
> {
> "href" : "http://localhost:8080/api/v1/clusters/c1?fields=alerts_summary";,
> "Clusters" : {
> "cluster_name" : "c1",
> "version" : "HDP-2.2"
> },
> "alerts_summary" : {
> "CRITICAL" : 0,
> "MAINTENANCE" : 0,
> "OK" : 48,
> "UNKNOWN" : 0,
> "WARNING" : 0
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
