Yes, its useful to have it. What this requires is a pre-defined service to be shipped with the Gateway. The following needs to be considered for that service.
1) The service context (path) should be preserved. We shouldn't allow APIs to be added with that context. 2) The gateway interceptors should ignore requests to this endpoint. i.e, security, throttling, analytics, etc should be ignored. Thanks, NuwanD. On Wed, Feb 1, 2017 at 12:05 PM, Rushmin Fernando <rush...@wso2.com> wrote: > +1 > > Other than sending back 200, I think it would be helpful if there is > another configuration to make the health check API, call a given backend > (which returns 200) and respond to the original caller. > > The advantage of having this is, we can have a rough idea about the full > flow. e.g. is traffic going out from the gateway node to outside networks? > > On Wed, Feb 1, 2017 at 11:44 AM, Lakmal Warusawithana <lak...@wso2.com> > wrote: > >> Hi, >> >> When we deploying api gateway in container management system (or even >> fronted by ELB) we need to have a health check end point to configure. >> Since gateway only going pass through we don't have such at the moment. >> >> Shall we do $subject? it should only return 200 >> >> thanks >> >> -- >> Lakmal Warusawithana >> Director - Cloud Architecture; WSO2 Inc. >> Mobile : +94714289692 <+94%2071%20428%209692> >> Blog : http://lakmalsview.blogspot.com/ >> >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Best Regards* > > *Rushmin Fernando* > *Technical Lead* > > WSO2 Inc. <http://wso2.com/> - Lean . Enterprise . Middleware > > mobile : +94775615183 > > > -- Nuwan Dias Software Architect - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
