OpenShift Logging: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
[[oc logs]] | [[oc logs]] | ||
=Master Process Logging= | =Master and Node Process Logging= | ||
==Master Process Logging== | |||
Adjust the logging level as described here: | |||
Then tail the journalctl log. | |||
[[journalctl]] -u atomic-openshift-master-controllers -f | |||
==Node Process Logging== | |||
Adjust the logging level as described here: | |||
Then tail the journalctl log. | |||
[[journalctl]] -u atomic-openshift-node -f | |||
=Main Application Traffic Proxy Logging= | =Main Application Traffic Proxy Logging= | ||
Revision as of 21:38, 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:
Then tail the journalctl log.
journalctl -u atomic-openshift-master-controllers -f
Node Process Logging
Adjust the logging level as described here:
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.