[jira] [Commented] (AMBARI-8084) Alerts: Convert Bigtop Stack Nagios Alerts

["Jonathan Hurley (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200487#comment-14200487 ] 

Jonathan Hurley commented on AMBARI-8084:
-----------------------------------------

See AMBARI-8165 for the Jira that tracks allowing Nagios to expose alert data from Ambari.

> Alerts: Convert Bigtop Stack Nagios Alerts
> ------------------------------------------
>
>                 Key: AMBARI-8084
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8084
>             Project: Ambari
>          Issue Type: Task
>          Components: alerts, ambari-server
>            Reporter: Newton Alex
>            Assignee: Jonathan Hurley
>             Fix For: 2.0.0
>
>
> Update the BT stack to start using the new Ambari alerting system.
> Here is the email from [~jonathan.hurley] for context:
> -----
> Hi Committers & Contributors,
> With Ambari 2.0, a new alerts framework has been implemented with the intent to replace Nagios. If you would like to learn more about this feature, the design documents can be found in the Jira epic at https://issues.apache.org/jira/browse/AMBARI-6354. 
> The work has been completed to move the HDP 2.x stack over from Nagios to the internal alerts framework. However, HDP 1.x and Bigtop have not yet been migrated. I would like to propose that we move all stacks off of Nagios so that we can remove that dependency from Ambari completely. 
> This also means that upon upgrading from a prior Nagios-enabled release of Ambari, Nagios will be removed as a dependent service. It will no longer be a part of the managed cluster.
> This will allow us to also remove any Nagios-specific areas of the codebase that would otherwise need to remain for legacy purposes. It would also relieve the requirement on clients to have intimate knowledge of which stack/version can be Nagios-enabled.
> ---------



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)