[AMBARI-8035] Alerts: Creating WEB Alert Definitions via REST API Drops URI

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: alerts, ambari-server
• Epic Link: Alerts Redesign
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 30/Oct/14 03:25
• Updated: 30/Oct/14 13:18
• Resolved: 30/Oct/14 12:23

Description

{
  "AlertDefinition" : {
    "cluster_name" : "c1",
    "component_name" : "NAMENODE",
    "enabled" : true,
    "interval" : 1,
    "label" : "AD Creation Test",
    "name" : "ad_creation_test",
    "scope" : "ANY",
    "service_name" : "HDFS",
    "source" : {
      "uri": {
      "http": "{{hdfs-site/dfs.namenode.http-address}}",
      "https": "{{hdfs-site/dfs.namenode.https-address}}",
      "https_property": "{{hdfs-site/dfs.http.policy}}",
      "https_property_value": "HTTPS_ONLY"
      },
      "reporting" : {
        "ok" : {
          "text" : "TCP OK - {0:.4f} response on port {1}"
        },
        "critical" : {
          "text" : "Connection failed: {0} on host {1}:{2}"
        }
      },
      "type" : "WEB"
    }
  }
}

Creates the alert successfully, but the URI parameter is missing. This does not affect alerts read from alerts.json

Issue Links

• links to: Reviewboard