ISSUE :
Even after configuring falcon to use https, ambari alert checks Falcon UI on http and fails. Falcon service will be running fine but Ambari shows Falcon WEB UI alert. ROOT CAUSE :
Ambari alert script is hardcoded to check Falcon on http WORKAROUND :
1. Login to Ambari UI
2. Open one more tab and go to this UI : http://AMBARI_HOST:8080/api/v1/clusters/CLUSTER_NAME/alert_definitions 3. Search for falcon_server_webui and get the alert definitions ID. Example : {
"href" : "http://mon-ravi.ironman.com:8080/api/v1/clusters/ironman/alert_definitions/301",
"AlertDefinition" : {
"cluster_name" : "ironman",
"id" : 301,
"label" : "Falcon Server Web UI",
"name" : "falcon_server_webui"
} 301 is the alert definition here.
4. Delete this alert definition using curl curl -u admin:admin -H "X-Requested-By: ambari" -X DELETE http://AMBARI_HOST:8080/api/v1/clusters/CLUSTER_NAME/alert_definitions/301 5. On the ambari server, edit this file /var/lib/ambari-server/resources/common-services/FALCON/0.5.0.2.1/alerts.json
Change
"http": "{{falcon-env/falcon_port}}",
to
"https": "{{falcon-env/falcon_port}}", 6. Restart Ambari server We should be all good now. Falcon web UI alert should clear up.
... View more
