Overview
It would be helpful to link to the unified log streams for each cluster from the UI. We could show a link to view all logs for the source or target cluster. It appears (looking at 3.11 and 4.6) that the URL to the logs is the same. We will need to resolve:
- the route name for the console
- the current pod name for mig-log-reader
There are a couple of options for how we could feed this info to UI. Perhaps the most suitable would be to provide a new endpoint on the discovery service that would feed back a logs URL for a particular MigCluster.
Sample OCP 3 unified logs URL
https://<console_url_here>/k8s/ns/openshift-migration/pods/migration-log-reader-5bc98b97cd-njhf6/logs
To build the URL above, we need
- the console URL (
oc get route console -n openshift-console)
- the migration-log-reader pod name (
oc get pod -n openshift-migration -l logreader=mig)

Sample OCP 4 unified logs URL
https://<console_url_here>/k8s/ns/openshift-migration/pods/migration-log-reader-7cc944f5d4-gmpt7/logs?container=plain
To build the URL above, we need
- the console URL (
oc get route console -n openshift-console
- the migration-log-reader pod name (
oc get pod -n openshift-migration -l logreader=mig)

Overview
It would be helpful to link to the unified log streams for each cluster from the UI. We could show a link to view all logs for the source or target cluster. It appears (looking at 3.11 and 4.6) that the URL to the logs is the same. We will need to resolve:
There are a couple of options for how we could feed this info to UI. Perhaps the most suitable would be to provide a new endpoint on the discovery service that would feed back a logs URL for a particular MigCluster.
Sample OCP 3 unified logs URL
To build the URL above, we need
oc get route console -n openshift-console)oc get pod -n openshift-migration -l logreader=mig)Sample OCP 4 unified logs URL
To build the URL above, we need
oc get route console -n openshift-consoleoc get pod -n openshift-migration -l logreader=mig)