MTC should provide more understandable feedback for its users (cluster admins) who:

• May have a migration stuck waiting on something, but it's unclear what is being waited on
• Are accustomed to using logs and events for granular feedback on controller activities
• Would like to understand what the controller is thinking at any given point in the migration
• Would like to understand all changes being made to their clusters, e.g. any API request modifying etcd store
• Expect to be able to easily filter for all logs for a particular migration across all system components
• Need context with all log messages so that they are able to locate whatever that log message is related to across clusters, namespaces, and kinds.
• Can't be expected to interpret or fix their own problem with a stack trace, can likely only send it to us
• May want to bump verbosity to get lower-level log messages e.g. from controller-runtime if they are seeing network-level issues etc.
• Don't necessarily know how to recover from a problem with the system even if they discovered what the problem was
• Don't know the set of CLI commands required to traverse our hierarchical API relationships looking for feedback on migration progress
• Don't know which Pod or CR to look at for an error message for the problem they are encountering
• Don't know which cluster to investigate on, since migration operations span up to 3 (host, src, target) clusters per migration