MaxScale does not log the root cause when a switchover/failover fails

We are requesting an enhancement to the mariadbmon logging in MaxScale. Currently, when a switchover or failover event fails, the error message provides no diagnostic information regarding why the operation failed.

Current Behavior: The log simply reports a generic failure: error :

[mariadbmon] Switchover test-mariadb-0 -> test-mariadb-2 failed.

Desired Behavior: The error log should include specific details about the failure condition. For example:

• Timeout waiting for replication catch-up
• Connection refused on target node
• Permission denied
• Specific SQL error returned during the promotion process

Business Impact / Motivation: Without detailed error messages, it is impossible to determine the root cause of high-availability failures (e.g., distinguishing between a MariaDB bug, a network issue, or a configuration error) without reproducing the issue with debug logging enabled. This increases Time to Resolution (TTR) for critical production outages.