[
https://issues.apache.org/jira/browse/AMBARI-21337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated AMBARI-21337:
---------------------------------
Description:
Request to add global SMTP settings which can be inherited by default by each
alert configuration (server, port, from, auth creds).
I'm seeing a customer with several alert configurations going to different
places and each one has the same SMTP details duplicated in each alert
notification which is redundant and will require changing in multiple places at
some point. Keeping the ability to override the settings for each alert
notification configuration is useful but it makes sense to have a single point
to configure the shared SMTP settings if they're not different.
The same thing applies to SNMP host, port and community string as they're most
likely going to be the same across different alert configurations.
was:
Request to add global SMTP settings which can be inherited by default by each
alert configuration (server, port, from, auth creds).
I'm seeing a customer with several alert configurations going to different
places and each one has the same SMTP details duplicated in each alert
notification which is redundant and will require changing in multiple places at
some point. Keeping the ability to override the settings for each alert
notification configuration is useful but it makes sense to have a single point
to configure the shared SMTP settings if they're not different.
Summary: Global SMTP & SNMP Alert settings (was: Global SMTP settings)
> Global SMTP & SNMP Alert settings
> ---------------------------------
>
> Key: AMBARI-21337
> URL: https://issues.apache.org/jira/browse/AMBARI-21337
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: 2.4.0
> Environment: HDP 2.5 + Kerberos
> Reporter: Hari Sekhon
> Priority: Minor
>
> Request to add global SMTP settings which can be inherited by default by each
> alert configuration (server, port, from, auth creds).
> I'm seeing a customer with several alert configurations going to different
> places and each one has the same SMTP details duplicated in each alert
> notification which is redundant and will require changing in multiple places
> at some point. Keeping the ability to override the settings for each alert
> notification configuration is useful but it makes sense to have a single
> point to configure the shared SMTP settings if they're not different.
> The same thing applies to SNMP host, port and community string as they're
> most likely going to be the same across different alert configurations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
