Related to #22151 issue. Could it be of the general interest to backport this? We have project that cannot make the upgrade to 2.4.x as they are in production and use intesively the RoutigDatasource. These ones are based in 2.2.9.
Comment From: philwebb
We discussed this today on our team call and decided that this really does feel like an enhancement and something that we'd prefer not to backport. Since it's possible to work around the issue by defining your own DB health indicator in earlier versions, we don't want to risk any instability in our maintenance releases.