Return-Path: X-Original-To: apmail-ambari-user-archive@www.apache.org Delivered-To: apmail-ambari-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F09BC18BEB for ; Thu, 18 Jun 2015 15:57:46 +0000 (UTC) Received: (qmail 44487 invoked by uid 500); 18 Jun 2015 15:57:46 -0000 Delivered-To: apmail-ambari-user-archive@ambari.apache.org Received: (qmail 44454 invoked by uid 500); 18 Jun 2015 15:57:46 -0000 Mailing-List: contact user-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ambari.apache.org Delivered-To: mailing list user@ambari.apache.org Received: (qmail 44444 invoked by uid 99); 18 Jun 2015 15:57:46 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jun 2015 15:57:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 2E0C7182234 for ; Thu, 18 Jun 2015 15:57:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=6.31 tests=[FSL_HELO_BARE_IP_2=0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id oqdEUsgyKFTI for ; Thu, 18 Jun 2015 15:57:34 +0000 (UTC) Received: from relayvx12c.securemail.intermedia.net (relayvx12c.securemail.intermedia.net [64.78.52.187]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id B6FC242B0E for ; Thu, 18 Jun 2015 15:57:33 +0000 (UTC) Received: from securemail.intermedia.net (localhost [127.0.0.1]) by emg-ca-1-2.localdomain (Postfix) with ESMTP id ED04053E64 for ; Thu, 18 Jun 2015 08:57:11 -0700 (PDT) Subject: Re: Ambari 2.1.0-snap: Alert configuration location MIME-Version: 1.0 x-echoworx-emg-received: Thu, 18 Jun 2015 08:57:11.951 -0700 x-echoworx-msg-id: c9a13bd0-9565-4e7c-b850-9bd9103bf251 x-echoworx-action: delivered Received: from 10.254.155.17 ([10.254.155.17]) by emg-ca-1-2 (JAMES SMTP Server 2.3.2) with SMTP ID 408 for ; Thu, 18 Jun 2015 08:57:11 -0700 (PDT) Received: from MBX080-W4-CO-1.exch080.serverpod.net (unknown [10.224.117.101]) by emg-ca-1-2.localdomain (Postfix) with ESMTP id BA65C53E64 for ; Thu, 18 Jun 2015 08:57:11 -0700 (PDT) Received: from MBX080-W4-CO-2.exch080.serverpod.net (10.224.117.102) by MBX080-W4-CO-1.exch080.serverpod.net (10.224.117.101) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Thu, 18 Jun 2015 08:57:10 -0700 Received: from MBX080-W4-CO-2.exch080.serverpod.net ([10.224.117.102]) by mbx080-w4-co-2.exch080.serverpod.net ([10.224.117.102]) with mapi id 15.00.1044.021; Thu, 18 Jun 2015 08:57:10 -0700 From: Jonathan Hurley To: "user@ambari.apache.org" Thread-Topic: Ambari 2.1.0-snap: Alert configuration location Thread-Index: AQHQqa2E+O1HBrM/N0u8Qy1V4tUp+J2ywYiAgAANbICAAAV8gIAADGqA Date: Thu, 18 Jun 2015 15:57:10 +0000 Message-ID: <5F666CCD-7AE1-41F4-99C6-2D16886DCDE5@hortonworks.com> References: <55829642.80708@uni.no> <1434636303775.42387@hortonworks.com> <1DC3FD32-E410-4535-AAE2-0B2DA0290DE6@hortonworks.com> <5582DFEB.7030208@uni.no> In-Reply-To: <5582DFEB.7030208@uni.no> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [173.71.90.39] x-source-routing-agent: Processed Content-Type: text/plain; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable Yes, they should be there. Was this an upgrade from an earlier Ambari 2.0 i= nstall? In which case they might not be there since the 2.0 definitions did= n=92t have them. Also, my below JSON had a syntax error in it, there should= be an extra closing {=20 > On Jun 18, 2015, at 11:12 AM, Eirik Thorsnes wrot= e: >=20 > On 18. juni 2015 16:53, Jonathan Hurley wrote: >> You can update the values, but you=92ll need to us the APIs to do this. >> When sending a new =93source=94 element, you need to include all fields = - it >> will not merge omitted source child elements in with the existing source= : >>=20 >> PUT api/v1/clusters//alert_definitions/ >=20 > Thank you, I'll try that. >=20 > Are the parameters section supposed to be already there in the definition= s? >=20 > If I issue a GET I only see the following: >=20 > GET -H 'X-Requested-By: ambari' > http://localhost:8080/api/v1/clusters/helm/alert_definitions/52 > { > "href" : > "http://localhost:8080/api/v1/clusters/helm/alert_definitions/52", > "AlertDefinition" : { > "cluster_name" : "helm", > "component_name" : "AMBARI_AGENT", > "description" : "This host-level alert is triggered if the amount of > disk space used on a host goes above specific thresholds. The default > values are 50% for WARNING and 80% for CRITICAL.", > "enabled" : true, > "id" : 52, > "ignore_host" : false, > "interval" : 1, > "label" : "Ambari Agent Disk Usage", > "name" : "ambari_agent_disk_usage", > "scope" : "HOST", > "service_name" : "AMBARI", > "source" : { > "path" : "alert_disk_space.py", > "type" : "SCRIPT" > } > } > } >=20 > Regards, > Eirik >=20 > --=20 > Eirik Thorsnes >=20 >=20