Comment 31 for bug 1700585

yes, the recommended existing tooling for alerting about this specific problem (unavailability) is swift-dispersion-report:

https://docs.openstack.org/developer/swift/admin_guide.html#geographically-distributed-swift-considerations

That might not be documented sufficiently, it came up at some point on the ML too:

http://lists.openstack.org/pipermail/openstack/2017-January/018327.html

The specifics of multi-region issue are described here:

https://docs.openstack.org/developer/swift/admin_guide.html#geographically-distributed-swift-considerations

Some general ideas about what you might *do* when the above monitoring techniques indicate there is a issue are described here:

https://docs.openstack.org/developer/swift/admin_guide.html#object-replicator

Some of the material here covers some of the mechanics of rebalance and might be useful:

https://www.youtube.com/watch?v=ger20cqOypE

Further enhancements to recon data might be the best implementable idea we have - so maybe this bug is just that feature. Always room to improve!