Desired Process

When the database is experiencing an outage/issue - receptor should reflect this status in the health status shown within API/v2/healthcheck & the topology visualizer.

Current Process

What happens now is the topology visualizer and healthcheck show all nodes as healthy even though in reality receptor service is now in a hung state because the database went offline/online.

Business Impact

Need this to properly monitor the environment for production executions in a multi cluster environment

Technical Impact

Receptor is hung and gives a false positive to the state of the cluster

Scale Impact

No scaling impact.