OpenShift Logging: Difference between revisions
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
==Master Process Logging== | ==Master Process Logging== | ||
Adjust the logging level as described here: | Adjust the logging level as described here: [[OpenShift_Change_the_Log_Level_for_OpenShift_Processes|Change the Log Level for OpenShift Processes]]. | ||
Then tail the journalctl log. | Then tail the journalctl log. | ||
| Line 27: | Line 27: | ||
==Node Process Logging== | ==Node Process Logging== | ||
Adjust the logging level as described here: | Adjust the logging level as described here: [[OpenShift_Change_the_Log_Level_for_OpenShift_Processes|Change the Log Level for OpenShift Processes]]. | ||
Then tail the journalctl log. | Then tail the journalctl log. | ||
Revision as of 21:39, 5 August 2017
Internal
Overview
This page is intended to provide the location of various types of logs in OpenShift.
Generic Pod Logging
oc logs [-f] <pod-name> [-c <container-name>]
For more details, see:
oc logs
Master and Node Process Logging
Master Process Logging
Adjust the logging level as described here: Change the Log Level for OpenShift Processes.
Then tail the journalctl log.
journalctl -u atomic-openshift-master-controllers -f
Node Process Logging
Adjust the logging level as described here: Change the Log Level for OpenShift Processes.
Then tail the journalctl log.
journalctl -u atomic-openshift-node -f
Main Application Traffic Proxy Logging
On the host that runs the application traffic HAProxy instance (appproxy.local), inspect /var/log/haproxy.log.