Enable live health for building block services
Jörg Gottschlich
meshStack should support building blocks outputting a health status url and display that status along with the BB in the project dashboard (and elsewhere).
Details:
I provide a service for my application via building block, e.g. a k8s cluster.
I want to see it's health status immediately in meshStack to understand if my application stack is healthy.
Therefore, meshStack should support a specific BB output (e.g.
ms_monitor_url
="https://some.service.url/health) which it regularly checks to get the health status of the service.Benefits for the user:
- Currently, I see green in meshStack if the BB run was successful (which is the first step). However, more important to me as a developer is if my service is healthy (second step). Therefore, I need to get this signal into my BB instance as suggested above.
- The BBD creator – who knows the service by heart – is the best person to define how to ping the state of the service afterwards. Therefore there should be a canonical way to surface that information to the service users.
- As a developer, if my application fails, I see immediately in meshStack if one of the depending services is responsible.
- meshStack can track the service health over time and provide an SLA report.
- This fosters best practice and resiliency in service provisioning.
- When applied consequently to a company's BB landscape, an aggregated view of service health across the company is easy to derive and useful for the insights for the overall platform health.