[
https://issues.apache.org/jira/browse/AMBARI-8978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yurii Shylov updated AMBARI-8978:
---------------------------------
Attachment: AMBARI-8978.patch
> 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)
