influxdata / influxdata/influxdb

Local time is not displayed correctly in Influx Dashboard

Open
#22,513 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.

1. Create a series of data points in the afternoon in your local timezone
2. Visualise the data in a dashboard

__Expected behavior:__
Describe what you expected to happen.
I expect times in the afternoon to be shown Either
in 24hr clock (like in UTC)
![image](https://user-images.githubusercontent.com/7541023/133926118-c2ced73d-f859-4667-abbd-f25a39f30fa4.png)

OR
With a PM suffix

__Actual behavior:__
Describe What actually happened.
You can see although the time period selected is from 18:00 it displays as 07:30
![image](https://user-images.githubusercontent.com/7541023/133926046-f69000eb-6d0e-4dea-ae93-345604521784.png)

__Environment info:__

* System info: Run `uname -srm` and copy the output here
[root@influx-vm azureuser]# uname -srm
Linux 3.10.0-1160.15.2.el7.x86_64 x86_64

* InfluxDB version: Run `influxd version` and copy the output here
[root@influx-vm azureuser]# influxd version
InfluxDB 2.0.8 (git: e91d41810f) build_date: 2021-08-13T18:22:30Z

* Other relevant environment details: Container runtime, disk info, etc

__Config:__
Copy any non-default config values here or attach the full config as a gist or file.

__Logs:__
Include snippet of errors in log.

__Performance:__
Generate profiles with the following commands for bugs related to performance, locking, out of memory (OOM), etc.

```sh
# Commands should be run when the bug is actively happening.
# Note: This command will run for ~30 seconds.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=30s"
iostat -xd 1 30 > iostat.txt
# Attach the `profiles.tar.gz` and `iostat.txt` output files.
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source file, test, or entry point. Reproduce the dashboard display using local-time data and compare the selected afternoon range with the rendered labels; done means afternoon times display in the expected 24-hour or PM-suffixed form.

Written by the indexing model from the issue text.

Assessment

Domain
data-visualization, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.