[
https://issues.apache.org/jira/browse/AMBARI-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-10625:
-----------------------------------------
Attachment: Screen Shot 2015-04-06 at 8.06.10 PM.png
> UI Improvements For Server Side Alerts
> --------------------------------------
>
> Key: AMBARI-10625
> URL: https://issues.apache.org/jira/browse/AMBARI-10625
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 2.1.0
>
> Attachments: Screen Shot 2015-04-06 at 8.06.10 PM.png
>
>
> https://issues.apache.org/jira/browse/AMBARI-10348 adds a new type of alert
> known as a server-side alert. These are used to run specialized classes
> inside of the Ambari JVM which can produce alerts without the need to run
> them on an agent. We currently use this for 2 types of alerts:
> - If a host goes down
> - If alerts have not run within 2x their normal interval values
> This new alert causes some display weirdness in the UI (see attachment).
> Seems like we need a new UI asset to assign as the icon for this new type of
> alert.
> As for alert properties, there's only 1 property right now which is the
> classname. Similar to script alerts, we can choose not to expose this value
> since nobody really should be changing it anyway.
> For fun, here's the JSON:
> {code:title=Server Alert Definition JSON}
> "AlertDefinition" : {
> "cluster_name" : "c1",
> "component_name" : "AMBARI_SERVER",
> "description" : "This alert is triggered if the server has lost contain
> with an agent.",
> "enabled" : true,
> "id" : 80,
> "ignore_host" : false,
> "interval" : 1,
> "label" : "Ambari Agent Heartbeat",
> "name" : "ambari_server_agent_heartbeat",
> "scope" : "HOST",
> "service_name" : "AMBARI",
> "source" : {
> "class" : "org.apache.ambari.server.alerts.AgentHeartbeatAlertRunnable",
> "type" : "SERVER"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
