Yes, they should be there. Was this an upgrade from an earlier Ambari 2.0
install? In which case they might not be there since the 2.0 definitions didn’t
have them. Also, my below JSON had a syntax error in it, there should be an
extra closing {
> On Jun 18, 2015, at 11:12 AM, Eirik Thorsnes <eirik.thors...@uni.no> wrote:
>
> On 18. juni 2015 16:53, Jonathan Hurley wrote:
>> You can update the values, but you’ll need to us the APIs to do this.
>> When sending a new “source” element, you need to include all fields - it
>> will not merge omitted source child elements in with the existing source:
>>
>> PUT api/v1/clusters/<cluster-name>/alert_definitions/<definition-id>
>
> Thank you, I'll try that.
>
> Are the parameters section supposed to be already there in the definitions?
>
> If I issue a GET I only see the following:
>
> 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"
> }
> }
> }
>
> Regards,
> Eirik
>
> --
> Eirik Thorsnes
>
>
