<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id="yui_3_16_0_ym19_1_1469512722586_9093"><span>Hi Sebastian,</span></div><div id="yui_3_16_0_ym19_1_1469512722586_9094"><span><br></span></div><div id="yui_3_16_0_ym19_1_1469512722586_9095"><span id="yui_3_16_0_ym19_1_1469512722586_9229">This type of feature can be very useful for liveness and readiness probes in a Kubernetes cluster [1].</span></div><div id="yui_3_16_0_ym19_1_1469512722586_9095"><span><br></span></div><div id="yui_3_16_0_ym19_1_1469512722586_9095"><span id="yui_3_16_0_ym19_1_1469512722586_9275">Maybe you can think at check status per-cache but also at whole server level.</span></div><div id="yui_3_16_0_ym19_1_1469512722586_9095"><span><br></span></div><div id="yui_3_16_0_ym19_1_1469512722586_9095" dir="ltr"><span>[1] </span><a href="http://kubernetes.io/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks" id="yui_3_16_0_ym19_1_1469512722586_9276">http://kubernetes.io/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks</a></div><div id="yui_3_16_0_ym19_1_1469512722586_9095" dir="ltr"><br></div><div id="yui_3_16_0_ym19_1_1469512722586_9095" dir="ltr">Thanks!</div><div></div><div id="yui_3_16_0_ym19_1_1469512722586_9096"> </div><div class="signature" id="yui_3_16_0_ym19_1_1469512722586_9300"><div dir="ltr" id="yui_3_16_0_ym19_1_1469512722586_9299"><div dir="ltr" id="yui_3_16_0_ym19_1_1469512722586_9298"><div dir="ltr" id="yui_3_16_0_ym19_1_1469512722586_9297"><div dir="ltr" id="yui_3_16_0_ym19_1_1469512722586_9296">--</div><div dir="ltr" id="yui_3_16_0_ym19_1_1469512722586_9301">Andrea Cosentino </div><div dir="ltr" id="yui_3_16_0_ym19_1_1469512722586_9302">----------------------------------</div><div dir="ltr" id="yui_3_16_0_ym19_1_1469512722586_9303">Apache Camel PMC Member</div><div dir="ltr" id="yui_3_16_0_ym19_1_1469512722586_9335">Apache Karaf Committer</div><div dir="ltr">Apache Servicemix Committer</div><div dir="ltr" id="yui_3_16_0_ym19_1_1469512722586_9336">Email: ancosen1985@yahoo.com</div><div dir="ltr" id="yui_3_16_0_ym19_1_1469512722586_9337">Twitter: @oscerd2</div><div dir="ltr" id="yui_3_16_0_ym19_1_1469512722586_9338">Github: oscerd</div></div></div></div></div> <div class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" style="display: block;"> <div style="font-family: Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 13px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"><font size="2" face="Arial"> On Tuesday, July 26, 2016 7:11 AM, Sebastian Laskawiec <slaskawi@redhat.com> wrote:<br></font></div> <br><br> <div class="y_msg_container"><div id="yiv7892648161"><div dir="ltr">Dear Community,<div><br></div><div>I'd like to ask you for help. I'm currently sketching a design for a REST health check endpoint for Infinispan and I'm trying to imagine possible use cases. </div><div><br></div><div>Could you please give me a hand and tell me what functionalities are important for you? Would you like to be able to check status per-cache or maybe a red (not healthy), green (healthy), yellow (healthy, rebalance in progress) cluster status is sufficient? What kind of information do you expect to be there?</div><div><br></div><div>Thanks</div><div>Sebastian</div></div></div><br>_______________________________________________<br>infinispan-dev mailing list<br><a ymailto="mailto:infinispan-dev@lists.jboss.org" href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br><br></div> </div> </div> </div></div></body></html>