<div dir="ltr"><div>Hi Markus,</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 15, 2021 at 4:52 AM Markus Demleitner <<a href="mailto:msdemlei@ari.uni-heidelberg.de">msdemlei@ari.uni-heidelberg.de</a>> wrote:</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">...<br>
<br>
I'm told CADC is using availability in internal processes -- but for<br>
that, we don't need to burden our standards, and we don't need to<br>
accept the disgrace that 10 years into VOSI's declaration that<br>
all services MUST implement VOSI a10y, only about 400 out of about<br>
23000 actually do (and the rest are thus in violation of a REC).<br>
<br></blockquote><div><br></div><div>Yes, all of our services (IVOA or not) implement /availability. They each do their own specific health check on resources on which they depend. We've also added an optional parameter 'detail=min' which will do nothing, but is handy as a 'ping' type probe to the service. The calls are made by nagios and our ops team gets alerts on failed calls or when they return false. We don't currently use mirrors, but we have multiple instances of services behind load balancers. Calls to /availability could hit any of those instances, so it's not particularly informative about server health, but it is good for those downstream dependency checks.</div><div><br></div><div>So, it's handy and useful to us, but we don't require it in any sort of interoperable way. I'm sure this has already been considered, but I think its value (if any) would lie with the operations interest group.</div><div><br></div><div>Cheers,</div><div>Brian</div></div></div>