@Jay Kumar SenSharma Thanks for your response. It resolves the issue. I realised that once i specify the appId, i can not collect multiple metrics with one call. Is there any workaround wheeeby i can specify appId for some metrics and not others in same call. These metrics are all using same appId (hbase). If i dont specify appId, the call returns the metrics for ams-hbase. Thanks ... View more

ok, i accepted an answer already. Thanks ... View more

Its ok. I am looking at a situation where i collect multiple metrics multiple metrics and extract them for storage in a database. Thanks anyways ... View more

@Jay Kumar SenSharma Okay thank you very much. I will to find a way of sorting them then. I appreciate ... View more

Hello @Jay Kumar SenSharma, Thanks for your continous help, it has been insightful. Anyways, i have noticed some behaviour while collecting metrics from the API. If for example i make an API call like so, http://*********/ws/v1/timeline/metrics?metricNames=dfs.FSNamesystem.BlockCapacity,dfs.FsVolume.FlushIoRateNumOps,jvm.file_descriptor_usage,Topologies,jvm.JvmMetrics.ThreadsTimedWaiting,jvm.threads.runnable.count,jvm.JvmMetrics.GcCount i get a response which is sorted in a strange manner like this below. Is there a special way API sorts the metrics in the response or is it just a random arrangement. Thanks { "metrics": [{ "timestamp": 1520030910000, "metadata": {}, "metricname": "jvm.JvmMetrics.ThreadsTimedWaiting", "appid": "applicationhistoryserver", "starttime": 1520030910000, "metrics": { "1520030910000": 29.0 } }, { "timestamp": 1520030910000, "metadata": {}, "metricname": "Topologies", "appid": "nimbus", "starttime": 1520030910000, "metrics": { "1520030910000": 0.0 } }, { "timestamp": 1520030910000, "metadata": {}, "metricname": "dfs.FSNamesystem.BlockCapacity", "appid": "n amenode", "starttime": 1520030910000, "metrics": { "1520030910000": 2097152.0 } }, { "timestamp": 1520030910000, "metadata": {}, "metricname": "dfs.FsVolume.FlushIoRateNumOps", "appid": "datanode", "starttime": 1520030910000, "metrics": { "1520030910000": 0.0 } }, { "timestamp": 1520030910000, "metadata": {}, "metricname": "jvm.file_descriptor_usage", "appid": "nifi", "starttime": 1520030910000, "metrics": { "1520030910000": 0.04996 } }, { "timestamp": 1520030910000, "metadata": {}, "metricname": "jvm.threads.runnable.count", "appid": "ambari_server", "starttime": 1520030910000, "metrics": { "1520030910000": 10.0 } } ] } ... View more

@Jay Kumar SenSharma Oh nice thats very good. Thanks I have also tried to use the wildcard (%) such that it can return all metrics per service but i always end up with an empty json response. Is it wrong to call for metrics as below; http://<ams-host>:6188/ws/v1/timeline/metrics?metricNames=regionServer.% Thanks for your help ... View more

Hello @Jay Kumar SenSharma Thanks for your feedback. Please how do i review the AMS datastore. Using this, can i get all the metrics per service? Thanks ... View more

Thank you very much @Jay Kumar SenSharma I am able to resolve it now Umar ... View more

Hello @Jay Kumar SenSharma since these certificates were generated by someone else i will like to delete them and create a fresh set of certificates together with readding the NIFI component to HDP. Kindly help will the proper certificate clearing and creation process. Thanks ... View more

Hello @Jay Kumar SenSharma my jdk version is as below. openjdk version "1.8.0_131" When i ran the command to check the certificates, i got the message below before the certificate chain message. CONNECTED(00000003) depth=1 OU = NIFI, CN = iot-node07.netvisor.local verify error:num=19:self signed certificate in certificate chain verify return:0 140187436160928:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:s3_pkt.c:1259:SS L alert number 42 140187436160928:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:184: --- Finally the permissions of the certificates were -rw------- Thanks ... View more

Thanks @Jay Kumar SenSharma i tried what you told me and the keystore password worked. But when i start the NIFI service, i still get the same error. So i tried to reinstall the nifi but i get the error below. 17/10/31 15:57:49 INFO properties.AESSensitivePropertyProvider: AES Sensitive Property Provider decrypted a sensitive value successfully Attempt to contact NiFi Node https://iot-node07.netvisor.local:9091/nifi did not complete due to exception: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors. Sleeping for 20 sec(s) 2017-10-31 15:58:10,335 - File['/var/lib/ambari-agent/cache/common-services/NIFI/1.0.0/package/files/nifi-toolkit-1.2.0.3.0.0.0-453/bin/node-manager.sh'] {'mode': 0755} 2017-10-31 15:58:13,004 - Will retry 14 time(s), caught exception: Error connecting to one or more nifi nodes: 17/10/31 15:58:11 INFO properties.NiFiPropertiesLoader: Loaded 124 properties from /usr/hdf/current/nifi/conf/nokedli/nifi.properties 17/10/31 15:58:12 INFO properties.ProtectedNiFiProperties: There are 4 protected properties of 5 sensitive properties (100%) 17/10/31 15:58:12 INFO properties.AESSensitivePropertyProvider: AES Sensitive Property Provider decrypted a sensitive value successfully 17/10/31 15:58:12 INFO properties.AESSensitivePropertyProvider: AES Sensitive Property Provider decrypted a sensitive value successfully 17/10/31 15:58:12 INFO properties.AESSensitivePropertyProvider: AES Sensitive Property Provider decrypted a sensitive value successfully 17/10/31 15:58:12 INFO properties.AESSensitivePropertyProvider: AES Sensitive Property Provider decrypted a sensitive value successfully Attempt to contact NiFi Node https://iot-node07.netvisor.local:9091/nifi did not complete due to exception: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors. Sleeping for 20 sec(s ... View more

Thanks @Jay SenSharma. I will try this out. To paint a better scenario, its an HDP cluster of 4 nodes but nifi is running on just one of them. Also, NIFI Certificate Authority is also installed. I thought with CA, i wont need to make any changes to the keystore. ... View more