Bug 1395654

Summary:	No documentation around --timestamps
Product:	OpenShift Container Platform	Reporter:	Jaspreet Kaur <jkaur>
Component:	Documentation	Assignee:	Michael Burke <mburke>
Status:	CLOSED WONTFIX	QA Contact:	Vikram Goyal <vigoyal>
Severity:	high	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	high
Version:	3.2.1	CC:	aos-bugs, jkaur, jokerman, mburke, mchappel, mmccomas
Target Milestone:	---	Flags:	mburke: needinfo? (jkaur) mburke: needinfo? (jkaur)
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-12-18 15:12:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jaspreet Kaur 2016-11-16 11:07:25 UTC

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

Comment 1 Michael Burke 2018-10-16 17:59:39 UTC

@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?