Hide Forgot
Document URL: https://access.redhat.com/documentation/en/openshift-enterprise/version-3.2/cluster-administration/ Section Number and Name: 16.4. Viewing Logs Describe the issue: There is no mention of different options that can be used with oc logs. Specifically oc logs <pod> --timestamps=true Which can help to resolve the issue mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1312947 pod logs are reported, when use --timestamps, in current local time - 1, which might be a summer/daylight savings time related issue, not sure. Suggestions for improvement: Please add a description for this option. Additional information: https://bugzilla.redhat.com/show_bug.cgi?id=1312947
@jaspreet In 3.10, the format for the oc log <pod> command is different than in 3.2 and it appears that the timestamp is included as GMT: [16/Oct/2018:17:52:55 +0000] oc log docker-registry-1-26244 --timestamps=true 2018-10-16T17:52:34.972966543Z 10.130.0.1 - - [16/Oct/2018:17:52:34 +0000] "GET /healthz HTTP/2.0" 200 0 "" "kube-probe/1.10+ oc log docker-registry-1-26244 --timestamps=false 10.130.0.1 - - [16/Oct/2018:17:52:55 +0000] "GET /healthz HTTP/2.0" 200 0 "" "kube-probe/1.10+" Can we close this BZ?