Although this will technically work, there is a supported way of doing this. The Falcon alert definition can specify the parameter to monitor for determining whether to use HTTP or HTTPS: {
"name": "falcon_server_webui",
"label": "Falcon Server Web UI",
"description": "This host-level alert is triggered if the Falcon Server Web UI is unreachable.",
"interval": 1,
"scope": "ANY",
"enabled": true,
"source": {
"type": "WEB",
"uri": {
"http": "{{falcon-env/falcon_port}}",
"https": "{{falcon-env/falcon_port}}",
"https_property": "{{hdfs-site/falcon.enableTLS}}",
"https_property_value": "true",
"default_port": 15000,
"kerberos_keytab": "{{falcon-startup.properties/*.falcon.http.authentication.kerberos.keytab}}",
"kerberos_principal": "{{falcon-startup.properties/*.falcon.http.authentication.kerberos.principal}}",
"connection_timeout": 5
},
"reporting": {
"ok": {
"text": "HTTP {0} response in {2:.3f}s"
},
"warning": {
"text": "HTTP {0} response from {1} in {2:.3f}s ({3})"
},
"critical": {
"text": "Connection failed to {1} ({3})"
}
}
}
}
Falcon should respect the port, regardless of plaintext vs encryption. However, this way, the alert framework will understand whether to use plaintext or TLS.
... View more
