[
https://issues.apache.org/jira/browse/AMBARI-8237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203926#comment-14203926
]
Jonathan Hurley commented on AMBARI-8237:
-----------------------------------------
It doesn't seem correct that this alert summary information is put on the alert
definition endpoint. When you request an alert definition, you should only get
the source of that definition. Instead, the alerts endpoint should host this
data, along with the ability to filter by any of the existing Alert properties
(such as definition name, host, date, etc).
The summary structure should also include the information required to give some
context to the summary counts, such as when the last state change occurred. I
proposed the following structure:
{code}
"alerts_summary" : {
"CRITICAL" : {
“count”: 2,
“original_timestamp”: 1415134996589
},
"OK” : {
“count”: 45,
“original_timestamp”: 1415134133489
}
...
}
{code}
> Alerts: Provide Summary Structure On Alerts Endpoint
> ----------------------------------------------------
>
> Key: AMBARI-8237
> URL: https://issues.apache.org/jira/browse/AMBARI-8237
> Project: Ambari
> Issue Type: Task
> Components: alerts, ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.0.0
>
>
> In the alert definitions summary page we show all the definitions along with
> counts of how many are OK, WARN, ERROR, etc. We need the alert instance
> counts rolled up into the alert definition response on cluster. This will
> save UI from getting all instances and then determining counts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
