-
Notifications
You must be signed in to change notification settings - Fork 477
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
Explain time zone of the lookback parameter #154
Comments
Sounds good. Is Also, as a bit of an aside, I'll add a note to the "Tags" info tooltip noting only exact matches are supported. |
Can you identify the timezone from the browser so that's it's always relevant to the user? |
Yes, we can get the timezone the browser is using, but, what timezone does the query-service generally interpret the date/time as? |
query-service doesn't interpret it, because UI is passing a Unix timestamp, which is relative to an absolute point in time, midnight of Jan 1 1970 in UTC time. |
Got it. Yes, I can add a note stating the time-values being entered are in local timezone of the browser and will be converted to UTC when sent to the server. |
"local" is good, but actually showing what it is is even better. |
@yurishkuro I agree, 100%. |
Moved from jaegertracing/jaeger#372
When "Custom Time Range" is specified, it would be good to show in which time zone the entered values are interpreted, either via
(?)
icon or explicitly "Start Time (TZ=New York [UTC-0500])".The text was updated successfully, but these errors were encountered: