[
https://issues.apache.org/jira/browse/AMBARI-6880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101042#comment-14101042
]
Jonathan Hurley commented on AMBARI-6880:
-----------------------------------------
Example of the new "alertDefinitionsCommands" field inside of an
{{AgentCommand}}
{code}
{
'alertDefinitionCommands':[
{
'alertDefinitions':[
{
'componentName':'NAMENODE',
'enabled':True,
'interval':2,
'name':'HDFS-Port',
'serviceName':'HDFS'
}
],
'clusterName':'c1',
'commandType':'ALERT_DEFINITION_COMMAND',
'hash':'b34f15f605892276f833af7cbc67647c',
'hostName':'c6404.ambari.apache.org'
}
]
}
{code}
> Alerts: Send Definitions Down Via Commands to the Agent
> -------------------------------------------------------
>
> Key: AMBARI-6880
> URL: https://issues.apache.org/jira/browse/AMBARI-6880
> Project: Ambari
> Issue Type: Task
> Affects Versions: 1.8.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 1.8.0
>
>
> Ambari agent hosts will receive the alert definitions they are responsible
> for scheudling via a new command type that is pushed down in the following
> scenarios:
> - Agent Registration
> - AlertDefinition invalidation
> The commands will be present in a heartbeat response if the server has
> determined that it thinks the agents need to be made away of which alert
> definitions are required to be scheduled. A hash value will also be sent
> along with the commands so that agents can decide if they do not need to
> reschedule their jobs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
