Active health checks for statically defined API services
Issue by varma09
Wednesday Sep 05, 2018 at 13:24 GMT
Originally opened as https://github.com/gizafoundation/api-layer/issues/89
As Sherman, I would like API layer to display service status in the API catalog based on the availability of the APIs and route only to active instances
Notes:
- Done in our Discovery Service instead of the service sending status to Eureka
Static service is automatically renewed by discovery service and no health monitoring is done. Routing to available instance is not present now, but is scheduled to be enabled in 20pi2
@plavjanik , this issue seems to be obsolete. Service tiles in the Catalog support three states: UP, DOWN and WARNING and those are visually indicated:

https://github.com/zowe/api-layer/blob/5db1b80bad9a6be6ebe381d91439cfcc3c9f40e6/api-catalog-ui/frontend/src/components/Tile/Tile.jsx#L45-L60
Hello @boris-bc, I do not think that is obsolete. It is not about just showing the status in the UI but actively monitoring statically defined services. Services that register dynamically to Eureka periodically sent status update. But for statically defined services no monitoring is done and the service is tracked as UP in Discovery Service no matter the real status.
The goal of this enhancement is have real status of any statically defined service provided by the Discovery Service.
This user story has been created after demonstrating the static definitions to Zowe architects who expressed interest in having status information correct for all the services.