Viewing Kubernetes logs

To view logging information, run the oc logs command from the command line.

There are three levels of detail at which you can report on the progress of pod and container installation:
Displaying pod status
Run the following command to see overall status for each pod.
oc get pods
Run the following command if the namespace is non-default.
oc get pods --n namespace
Where namespace is the name of the non-default namespace.
Displaying a log file
Run the following command to display log files for a specific pod or container within that pod.
oc logs name_of_pod [-c name_of_container]
The following section lists the relevant commands for the different pods and containers.
Primary ObjectServer
oc logs name_of_objserv-primary-pod
Backup ObjectServer
oc logs name_of_objserv-backup-pod -c ncobackup-agg-b
Failover gateway
oc logs name_of_objserv-backup-pod -c ncobackup-agg-gate
WebGUI
oc logs name_of_webgui-pod -c webgui 
Log Analysis
oc logs name_of_log-analysis-pod -c unity
XML gateway
oc logs name_of_log-analysis-pod -c gateway
Primary Impact Server
oc logs name_of_impactcore-primary-pod -c nciserver
Backup Impact Server
oc logs name_of_impactcore-backup-pod -c nciserver
Impact GUI Server
oc logs name_of_impactgui-pod -c impactgui
Proxy
oc logs name_of_proxy-pod
OpenLDAP
oc logs name_of_OpenLDAP-pod
cloud native analytics
oc logs name_of_cassandra-pod
oc logs name_of_couchdb-pod
oc logs name_of_ea-noi-layer-eanoigateway-pod
oc logs name_of_ea-noi-layer-eanoiactionservice-pod
oc logs name_of_ibm-hdm-analytics-dev-inferenceservice-pod
oc logs name_of_ibm-hdm-analytics-dev-eventsqueryservice-pod
oc logs name_of_ibm-hdm-analytics-dev-archivingservice-pod
oc logs name_of_ibm-hdm-analytics-dev-servicemonitorservice-pod
oc logs name_of_ibm-hdm-analytics-dev-policyregistryservice-pod
oc logs name_of_ibm-hdm-analytics-dev-ingestionservice-pod
oc logs name_of_ibm-hdm-analytics-dev-trainer-pod
oc logs name_of_ibm-hdm-analytics-dev-collater-aggregationservice-pod
oc logs name_of_ibm-hdm-analytics-dev-normalizer-aggregationservice-pod
oc logs name_of_ibm-hdm-analytics-dev-dedup-aggregationservice-pod
oc logs name_of_spark-master-pod
oc logs name_of_spark-slave-pod
oc logs name_of_ea-ui-api-graphql-pod
oc logs name_of_ibm-hdm-common-ui-uiserver-pod
oc logs name_of_zookeeper-pod
oc logs name_of_redis-sentinel-pod
oc logs name_of_redis-server-pod
Following a log file
Run the following command to stream a log file for a specific pod or container within that pod.
oc logs -f name_of_pod [-c name_of_container]
The following section lists the relevant commands for the different pods and containers.
Primary ObjectServer
oc logs -f --tail=1 name_of_objserv-primary-pod
Backup ObjectServer
oc logs -f --tail=1 name_of_objserv-backup-pod -c ncobackup-agg-b
Failover gateway
oc logs -f --tail=1 name_of_objserv-backup-pod -c ncobackup-agg-gate
WebGUI
oc logs -f --tail=1 name_of_webgui-pod -c webgui
Log Analysis
oc logs -f --tail=1 name_of_log-analysis-pod -c unity
XML gateway
oc logs -f --tail=1 name_of_log-analysis-pod -c gateway
Primary Impact Server
oc logs -f --tail=1 name_of_impactcore-primary-pod -c nciserver
Backup Impact Server
oc logs -f --tail=1 name_of_impactcore-backup-pod -c nciserver
Impact GUI Server
oc logs -f --tail=1 name_of_impactgui-pod -c impactgui
Proxy
oc logs -f --tail=1 name_of_proxy-pod
OpenLDAP
oc logs -f --tail=1 name_of_OpenLDAP-pod
cloud native analytics
oc logs -f --tail=1 name_of_cassandra-pod
oc logs -f --tail=1 name_of_couchdb-pod
oc logs -f --tail=1 name_of_ea-noi-layer-eanoigateway-pod
oc logs -f --tail=1 name_of_ea-noi-layer-eanoiactionservice-pod
oc logs -f --tail=1 name_of_ibm-hdm-analytics-dev-inferenceservice-pod
oc logs -f --tail=1 name_of_ibm-hdm-analytics-dev-eventsqueryservice-pod
oc logs -f --tail=1 name_of_ibm-hdm-analytics-dev-archivingservice-pod
oc logs -f --tail=1 name_of_ibm-hdm-analytics-dev-servicemonitorservice-pod
oc logs -f --tail=1 name_of_ibm-hdm-analytics-dev-policyregistryservice-pod
oc logs -f --tail=1 name_of_ibm-hdm-analytics-dev-ingestionservice-pod
oc logs -f --tail=1 name_of_ibm-hdm-analytics-dev-trainer-pod
oc logs -f --tail=1 name_of_ibm-hdm-analytics-dev-collater-aggregationservice-pod
oc logs -f --tail=1 name_of_ibm-hdm-analytics-dev-normalizer-aggregationservice-pod
oc logs -f --tail=1 name_of_ibm-hdm-analytics-dev-dedup-aggregationservice-pod
oc logs -f --tail=1 name_of_spark-master-pod
oc logs -f --tail=1 name_of_spark-slave-pod
oc logs -f --tail=1 name_of_ea-ui-api-graphql-pod
oc logs -f --tail=1 name_of_ibm-hdm-common-ui-uiserver-pod
oc logs -f --tail=1 name_of_ea-ui-api-graphql-pod
oc logs -f --tail=1 name_of_kafka-pod
oc logs -f --tail=1 name_of_zookeeper-pod
oc logs -f --tail=1 name_of_redis-sentinel-pod
oc logs -f --tail=1 name_of_redis-server-pod
Draft comment: LOUISERoberts
#4658 Needs triage/work