[
https://issues.apache.org/jira/browse/AMBARI-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-7094:
------------------------------------
Description:
Alert Targets should have the ability to contain an unstructured set of
properties so that customer defined targets (and dispatchers) can still be
stored and retrieved by Ambari.
The initial design had a defined structure for both email and snmp protocols.
However, these properties were just turned into a flat set by the data layer.
For the initial approach, it doesn't make much sense to try to model structured
properties when, at the end of the day, they need to be serialized to a map.
{code}
{
"AlertTarget": {
"name": "Administrators",
"description": "The Admins",
"notification_type": "EMAIL",
"properties":{
"mail.smtp.host": "my.host.net",
"mail.smtp.port" : "587",
...
}
}
}
{code}
This also lets any property defined be passed to the backend provider in order
to properly dispatch to the targets.
was:
Alert Targets should have the ability to contain an unstructured set of
properties so that customer defined targets (and dispatchers) can still be
stored and retrieved by Ambari.
The initial design had a defined structure for both email and snmp protocols.
However, these properties were just turned into a flat set by the data layer.
For the initial approach, it doesn't make much sense to try to model structured
properties when, at the end of the day, they need to be serialized to a map.
{code}
{
"AlertTarget": {
"name": "Administrators",
"description": "The Admins",
"notification_type": "EMAIL",
"properties":{
"mail.smtp.host": "my.host.net",
"mail.smtp.port" : "587",
...
}
}
}
{code}
> Alerts: Implement Property Updates for Alert Targets
> ----------------------------------------------------
>
> Key: AMBARI-7094
> URL: https://issues.apache.org/jira/browse/AMBARI-7094
> Project: Ambari
> Issue Type: Task
> Affects Versions: 1.8.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 1.8.0
>
>
> Alert Targets should have the ability to contain an unstructured set of
> properties so that customer defined targets (and dispatchers) can still be
> stored and retrieved by Ambari.
> The initial design had a defined structure for both email and snmp protocols.
> However, these properties were just turned into a flat set by the data layer.
> For the initial approach, it doesn't make much sense to try to model
> structured properties when, at the end of the day, they need to be serialized
> to a map.
> {code}
> {
> "AlertTarget": {
> "name": "Administrators",
> "description": "The Admins",
> "notification_type": "EMAIL",
> "properties":{
> "mail.smtp.host": "my.host.net",
> "mail.smtp.port" : "587",
> ...
> }
> }
> }
> {code}
> This also lets any property defined be passed to the backend provider in
> order to properly dispatch to the targets.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
