OpenShift Logging: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 17: Line 17:
=Master and Node Process Logging=
=Master and Node Process Logging=


==Master Process Logging==
{{Internal|OpenShift_Runtime#Master_and_Node_Process_Logging|OpenShift Runtime Operations - Master and Node Process Logging}}


Adjust the logging level as described here: [[OpenShift_Change_the_Log_Level_for_OpenShift_Processes|Change the Log Level for OpenShift Processes]].
=Management Traffic Proxy Logging=


Then tail the journalctl log.  
On the host that runs the API/Master Console traffic HAProxy instance, inspect /var/log/haproxy.log.
 
[[journalctl]] -u atomic-openshift-master-controllers -f
 
==Node Process Logging==
 
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.  
 
[[journalctl]] -u atomic-openshift-node -f


=Main Application Traffic Proxy Logging=
=Main Application Traffic Proxy Logging=

Latest revision as of 19:43, 2 November 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

OpenShift Runtime Operations - Master and Node Process Logging

Management Traffic Proxy Logging

On the host that runs the API/Master Console traffic HAProxy instance, inspect /var/log/haproxy.log.

Main Application Traffic Proxy Logging

On the host that runs the application traffic HAProxy instance (appproxy.local), inspect /var/log/haproxy.log.

Infrastructure Services

Kibana

Kibana Logging in OpenShift