[jira] [Commented] (AMBARI-8978) Alerts: Allow Ability To Test An AlertTarget Before Creating It

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-8978:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12689861/AMBARI-8978.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 5 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/1145//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1145//console

This message is automatically generated.

> 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
>
>         Attachments: AMBARI-8978.patch
>
>
> 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)