Apparently, haproxy is lacking proper logging on dbproxy roles (or at least, dbproxy1002), but I remember reading logs of why failovers happen and when. It would be nice to have those on journalctl for easy debugging when connection or other failures happen.
This is motivated by a recent dbproxy1002 losing connectivity towards db1062 (m2 master), causing a brief period of read only.
We should may also increase the timeouts so they take more than 10 seconds of unavailability to proceed to a failover, given how much time it takes for the service to be back into good state afterwards (and requires human intervention- e.g. maybe in the order of 60 seconds).