Note: AMS sink adds the client/service to the metric name, as far as I remember Ganglia does not handle it this way.
Ganglia add port number to the metric name instead. So these metrics will not show up with Ganglia metrics. You can try to find out what the name of the metric is by look at the rrd file names in /var/lib/ganglia/rrds Then use UI or API to change the widget definition to pull that metric. BR, Sid ________________________________ From: Siddharth Wagle <[email protected]> Sent: Wednesday, September 07, 2016 9:10 AM To: [email protected] Subject: Re: About Ganglia configuration in hadoop-metrics2.properties.j2 Hi Rui Gao, Ambari no longer support Ganglia in version 2.1.0. Instead Ambari Metrics Service provides better capability to scale with regards to growing cluster size as well as customized dashboard based visualizations using Grafana. Regarding you question regarding the ports: Is the NN configured to listen on different ports for clients and datanodes? hdfs-site :: dfs.namenode.servicerpc-address Again these settings that you have below: rpcdetailed.rpcdetailed.client.CompleteAvgTime and rpcdetailed.rpcdetailed.datanode.CompleteAvgTime are verified to work with AMS backend in 2.2.2 and not Ganglia. https://cwiki.apache.org/confluence/display/AMBARI/Metrics BR, Sid ________________________________ From: Rui Gao <[email protected]> Sent: Wednesday, September 07, 2016 1:13 AM To: [email protected] Subject: About Ganglia configuration in hadoop-metrics2.properties.j2 Hello everyone, Nice to meet you all. I'm Gao, an engineer working in Japan. I'm using Ambari to deploy Hadoop clusters, and using ganglia to monitor clusters. In a cluster using Ambari Version 2.2.2.0, thanks to hadoop-metrics2.properties.j2, we could got following configurations in hadoop-metrics2.properties of namenodes: #Namenode rpc ports customization namenode.sink.timeline.metric.rpc.client.port=${rpc_port} namenode.sink.timeline.metric.rpc.datanode.port=${serviceRPC_port} These configurations help us to monitor the ports respectively in Ambari WebUI as two groups: rpcdetailed.rpcdetailed.client.CompleteAvgTime and rpcdetailed.rpcdetailed.datanode.CompleteAvgTime . I want to monitor these ports separately in ganglia, so we add #Namenode rpc ports customization namenode.sink.timeline.metric.rpc.client.port=${rpc_port} namenode.sink.timeline.metric.rpc.datanode.port=${serviceRPC_port} #Namenode rpc ports customization(ganglia) namenode.sink.ganglia.metric.rpc.client.port=${rpc_port} namenode.sink.ganglia.metric.rpc.datanode.port=${serviceRPC_port} in the testing cluster, which using Ambari Version 2.2.1.1, but we still can only get the metrics of one port. And can only get rpcdetailed.rpcdetailed.CompleteAvgTime, not "rpcdetailed.rpcdetailed.client.CompleteAvgTime and rpcdetailed.rpcdetailed.datanode.CompleteAvgTime" respectively. I wonder to ask that is there anyone knows how to get separated ports metrics for ganglia by editing ambari Hadoop-metrics2.properties.j2 file? And, is separated port monitoring can only be possible in Ambari Version 2.2.2.0 and newer versions, not supported in Ambari Version 2.2.1.1? Or, just I made mistakes about the configuration? Looking forward to your reply! Thank you very much! Best regards, Gao
