You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
Hi,
kspan emits events in UTC, e.g:
This causes traces not being shown unless the Loopback dropdown is set to "Last 2 Hours".
The text was updated successfully, but these errors were encountered: