Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 2 Jan 2015 18:02:34 +0000 (UTC)
From: "Yurii Shylov (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12764631.1420221716000.75.1420221754432@Atlassian.JIRA>
In-Reply-To: <JIRA.12764631.1420221716000@Atlassian.JIRA>
References: <JIRA.12764631.1420221716000@Atlassian.JIRA>
 <JIRA.12764631.1420221716557@arcas>
Subject: [jira] [Created] (AMBARI-8978) Alerts: Allow Ability To Test An
 AlertTarget Before Creating It
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Yurii Shylov created AMBARI-8978:
------------------------------------

             Summary: Alerts: Allow Ability To Test An AlertTarget Before Creating It
                 Key: AMBARI-8978
                 URL: https://issues.apache.org/jira/browse/AMBARI-8978
             Project: Ambari
          Issue Type: Task
          Components: ambari-server
    Affects Versions: 2.0.0
            Reporter: Yurii Shylov
            Assignee: Yurii Shylov
             Fix For: 2.0.0


During the cluster installation, the web client would like to be able to have the administrator configure an alert target for use with that cluster. However, because there are many properties that are used to successfully create an AlertTarget, it's likely that the settings originally provided may not work.

For example, when creating an AlertTarget for SMTP, if the security or port are not valid (or the SMTP server is restricting access to certain IP addresses) then the target won't be able to properly use it.

We need to be able to allow an AlertTarget to be "tested" before actually creating it in the system. 

I propose a new endpoint off of targets that can be used to POST to. The POST can contain all of the alert properties that would normally be found on an AlertTarget. The difference is that no target is created; instead a status is returned about whether the target works (and why it doesn't if it failed).

I would suggest also altering the dispatcher interface to support a new method; something like {{Dispatcher.testAlertTarget(...)}} which will simply exercise the properties of the target to ensure a good connection.


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