search

AnalogJ / scrutiny

Hard Drive S.M.A.R.T Monitoring, Historical Trends & Real World Failure Thresholds
MIT License
4.98k stars 164 forks source link

[BUG] WebUI doesnt show proper time #348

Open UltraHKR opened 2 years ago

UltraHKR commented 2 years ago

Describe the bug The temp graph doesnt show the proper (adjusted to timezone) time. I use "America/Guayaquil", my local timezone, but temp graph keeps showing GMT time.

Expected behavior HDD last update time should match the temp graph loosely........

Screenshots image

[docker compose..yml]

version: "3.3" services: scrutiny: image: ghcr.io/analogj/scrutiny:master-omnibus container_name: scrutiny environment:

The log files will be available on your host in the config directory. Please attach them to this issue. (There are NO log files there....) docker logs scutiny: smartscrutiny.log.txt

Please also provide the output of docker info

Client: Context: default Debug Mode: false Plugins: app: Docker App (Docker Inc., v0.9.1-beta3) buildx: Docker Buildx (Docker Inc., v0.7.1-docker) scan: Docker Scan (Docker Inc., v0.12.0)

Server: Containers: 26 Running: 21 Paused: 0 Stopped: 5 Images: 22 Server Version: dev Storage Driver: zfs Zpool: V3700-JBOD Zpool Health: ONLINE Parent Dataset: V3700-JBOD/Docker_Data Space Used By Parent: 29105191440 Space Available: 4520819491888 Parent Quota: no Compression: lz4 Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc Default Runtime: runc Init Binary: docker-init containerd version: 7b11cfaabd73bb80907dd23182b9347b4245eb5d runc version: v1.0.2-0-g52b36a2 init version: de40ad0 Security Options: apparmor Kernel Version: 5.10.120+truenas Operating System: Debian GNU/Linux 11 (bullseye) OSType: linux Architecture: x86_64 CPUs: 6 Total Memory: 47.06GiB Name: truenas ID: AZO6:CTLV:DKMN:7HZV:TIEH:AR2D:JKSF:BACB:SEOD:55D2:KXLE:SHJT Docker Root Dir: /mnt/V3700-JBOD/Docker_Data Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false

AnalogJ commented 2 years ago

Good catch, I'll take a look at this. Local vs Remote timezone issues are usually kind of annoying to debug, so I can't guarantee that this will be fixed quickly, but it's definitely on the list now.

Thanks!

UltraHKR commented 2 years ago

maybe a temporal compromise could be treating user defined timezone as "local time"?