-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Metrics UI] All the times on the Elastic Charts are using UTC instead of the browser timezone #122683
Comments
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
@monfera @elastic/elastic-charts can someone weigh in here? If the above ticket description is wholly accurate, this would be a pretty wide-reaching bug, I'd imagine? |
Question: If we specify a timezone value to the chart, which should it be? There is a Kibana advanced setting for this but I don't know if we use that in observability apps already. @elastic/infra-monitoring-ui does anybody know if we have a precedent for that? |
APM gets the timezone from uiSettings and passes it into the series. I think it's done for each chart (most charts use the TimeSeriesChart but they are all just using Elastic Charts) kibana/x-pack/plugins/apm/public/components/app/error_group_details/Distribution/index.tsx Lines 84 to 121 in a787a30
|
The proposed solution is the best choice to do to be fully sure and under control of the timezone used. Another quick comment: this is not caused directly by the |
Kibana version:
7.16.2+
Elasticsearch version:
7.16.2+
Original install method (e.g. download page, yum, from source, etc.):
Any
Describe the bug:
All the Elastic Charts in the Metrics UI are displaying UTC on the X-Axis. This issue was introduced in elastic/elastic-charts#1383 and appearded in 7.16.2. Anything that is using the
niceTimeFormatter
and relying on the default behavior is affected by this bug. The solution is to add the browser'stimezone
param to theBarChart
component.Steps to reproduce:
Expected behavior:
The time should be displayed in local time.
The text was updated successfully, but these errors were encountered: