I'm not sure what you mean when you say "turn down" the process. If you are shutting down the process, then the port is released and the alert will not be able to make a socket connection. You will get a CRITICAL right away. The values in the alert are a round-trip-time coupled with a socket read time. For the warning, it will attempt to make a socket connection and if it succeeds and releases in under 1.5 seconds, then there's no warning. Because you set the CRITICAL value to 3600s but stopped the process, it's not going to wait 3600 since it can detect much faster that the port is not open for a socket connection.
On Mar 24, 2017, at 2:40 PM, Ganesh Viswanathan <gan...@gmail.com<mailto:gan...@gmail.com>> wrote: I am using Ambari's "HBase Regionserver Process" alert with 1.5s as WARNING threshold and 3600s as CRITICAL threshold. However, when I test this by turning down the regionserver process, the alert fires off as CRITICAL directly. Is this a bug? I am using HDP2.4 with Ambari 2.2.1.0<http://2.2.1.0/>: https://docs.hortonworks.com/HDPDocuments/Ambari-2.2.1.0/bk_Ambari_Users_Guide/content/_hbase_service_alerts.html Thanks, Ganesh
