Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kspan emits events in UTC #6

Open
felipecruz91 opened this issue Mar 22, 2021 · 1 comment
Open

kspan emits events in UTC #6

felipecruz91 opened this issue Mar 22, 2021 · 1 comment

Comments

@felipecruz91
Copy link

Hi,

kspan emits events in UTC, e.g:

{"ref": "replicaset:default/nginx-6799fc88d8", "name": "Deployment.ScalingReplicaSet", "start": "15:27:24.000", "end": "15:27:24.000"}

This causes traces not being shown unless the Loopback dropdown is set to "Last 2 Hours".

@bboreham
Copy link
Collaborator

Hi, I was hesitant to comment here because my own timezone was UTC, but since Sunday we've been in BST and I haven't noticed any problem viewing spans. They are emitted on my Kubernetes cluster in UTC and displayed in Jaeger in my local timezone.

I believe that emitting timestamps in UTC is correct; this is the one thing guaranteed to be consistent for all actors. Rendering the time in local timezone is a job for the final UI.

Maybe something is interfering with Jaeger understanding your local timezone?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants