Thank you for the confirmation. Until the, I suppose we can just head into postgres on an add-needed basis. I don't want to keep this postgres python code in, since it inhibits who can run the audit tool (only a specific service account). ... View more

The second was what I was looking for. Thanks! ... View more

We have the same issue with one particular user. The query works fine as other users. I have checked permissions under .hiveJars and the like. ... View more

I tried the cpu host call, but it gives me: curl: (3) [globbing] error: bad range specification after pos 101 And yes, I know the below is an old Unix date, which I did replace with something like Start:1491309675 ("04/04/2017 08:41:15") End: 1491481119 (Thu Apr 6 08:18:31 EDT 2017) I'm not sure what the 15 signifies, or the end '&_=1430848217591' [mtdeguzis@HOST ~]$ curl -k -H "X-Requested-By: ambari" -u <MYUSERNAME> -X GET <a href="http://<AMBARI_HOST>http://:api/v1/clusters//hosts/?fields=metrics/cpu/cpu_user[1430844610,1430848210,15],metrics/cpu/cpu_wio[1430844610,1430848210,15],metrics/cpu/cpu_nice[1430844610,1430848210,15],metrics/cpu/cpu_aidle[1430844610,1430848210,15],metrics/cpu/cpu_system[1430844610,1430848210,15],metrics/cpu/cpu_idle[1430844610,1430848210,15]&_=1430848217591</a>>:<PORT>api/v1/clusters/<CLUSTER_NAME>/hosts/<TARGET_HOST>?fields=metrics/cpu/cpu_user[1430844610,1430848210,15],metrics/cpu/cpu_wio[1430844610,1430848210,15],metrics/cpu/cpu_nice[1430844610,1430848210,15],metrics/cpu/cpu_aidle[1430844610,1430848210,15],metrics/cpu/cpu_system[1430844610,1430848210,15],metrics/cpu/cpu_idle[1430844610,1430848210,15]&_=1430848217591 curl -k -H "X-Requested-By: ambari" -u mtdeguzis -X GET "http://<AMBARI_HOST>:<PORT>/api/v1/clusters/<CLUSTER_NAME>/hosts/<TARGET_HOST>?fields=metrics/cpu/cpu_user[1491309675,1491481119,15]" ... View more

This looks to be what I need, I see the CPU call there for the host, thank you 🙂 ... View more