Thank you Aravindan. - clusterHostInfo is not available in alert script - for znode path we will require zookeeper client on that host - we are not aware of host on which METRIC_COLLECTOR's are installed.
So we are planning to use ambari API http://<AMBARI_SERVER_HOST>:8080/api/v1/clusters/<CLUSTER_NAME>/services/AMBARI_METRICS/components/METRICS_COLLECTOR?fields=host_components/HostRoles/host_name to fetch hostname. Just want to understand why is config.clusterHostInfo not available in alert scripts? On Thu, Jul 12, 2018 at 11:15 PM, Aravindan Vijayan < [email protected]> wrote: > Hi Saloni, > > > > When you have multiple metrics collectors all of them are active. Any one > of them can be used. > > > > FYI, there are 3 lookup options for the list of collectors. > > * Ambari Cluster Host info. > * Zookeeper znode path (/ambari-metrics-cluster/LIVEINSTANCES) > * Response to http://<ANY_COLLECTOR_HOST>:6188/ws/v1/timeline/metrics/ > livenodes > > > > -- > > Thanks and Regards, > > Aravindan Vijayan > > > > On 7/12/18, 8:26 AM, "saloni udani" <[email protected]> wrote: > > > > We have developed a custom script based alert for our ambari service > which > > triggers alert based on some ambari metric value. For fetching this > metric > > value, the metric collector hostname and port is required. It seems > that > > clusterHostInfo configuration is not available in alert script, so we > > referred to timeline.metrics.service.webapp.address. Everthing works > as > > expected. But now the issue arises when we configure metric service in > HA > > mode. For metric service to work in HA mode > > timeline.metrics.service.webapp.address cannot be changed to hostname > as we > > previously did. > > > > So from where can we get active metric collector hostname? > > >
