health-monitoring

I am using Docker version 17.09.0-ce I see that containers are marked as unhealthy incase of health check failures. Is there an option to get the container restart instead of keeping the container as unhealthy. Restarting of unhealty container feature was in the original PR ( https://github.com/moby/moby/pull/22719 ), but was removed after a discussion and considered to be done later as enhancement of RestartPolicy. At this moment you can use this workaround to automatically restarting unhealty containers: https://hub.docker.com/r/willfarrell/autoheal/ Here is a sample compose file: version:

I am using the HDP Sample and I have a Blood pressure sensor (http://www.andonline.com/medical/products/details.php?catname=&product_num=UA-767PBT-C). I get the data from it, but I don't know how to parse it into something human readable. this is what I tried until now with something like: while(fis.read(data) > -1) { String value = null; BigInteger bi = new BigInteger(data); // for(byte b:data){ // value+=b; // } Log.d("read data binary", "the data "+bi.toString(2)); Log.d("read data decimal", "the data "+bi.toString()); Log.d("read data hexa", "the data "+bi.toString(16)); Log.d("read data

I'm looking for the best way to log errors in an ASP.NET application. I want to be able to receive emails when errors occurs in my application, with detailed information about the Exception and the current Request. In my company we used to have our own ErrorMailer, catching everything in the Global.asax Application_Error. It was "Ok" but not very flexible nor configurable. We switched recently to NLog. It's much more configurable, we can define different targets for the errors, filter them, buffer them (not tried yet). It's a very good improvement. But I discovered lately that there's a whole

I have a Response.Redirect in my Employee page. It redirects to Salary page. Response.Redirect ("Salary.aspx"); It was working fine until I added exception handling as below. try { Response.Redirect ("Salary.aspx"); } catch(Exception ex) { //MyLog(); throw new Exception(); } //Remaining code in event handler This caused a new exception saying "Thread was being aborted”. I came to know that this can be avoided by setting endResponse as false for the redirect. Response.Redirect(url, false); Context.ApplicationInstance.CompleteRequest(); Explanation of new exception: It always throws the

I am using Hibernate in my JBoss war, using c3p0 for connection pooling, both configured within a hibernate.cfg.xml config file in my classpath <property name="connection.provider_class">org.hibernate.connection.C3P0ConnectionProvider</property> I've seen server.log generates lines with interesting information about the connection pool: DEBUG [com.mchange.v2.resourcepool.BasicResourcePool] trace com.mchange.v2.resourcepool.BasicResourcePool@63f5e4b6 [managed: 10, unused: 9, excluded: 0] For my monitoring pool (I am using nagios) I'd like to provide a JSP telling how many connections are being