Skip to content
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

summer->winter time changeover looks bad on the graph #5256

Open
1 task done
patrickhafner opened this issue Oct 27, 2024 · 2 comments
Open
1 task done

summer->winter time changeover looks bad on the graph #5256

patrickhafner opened this issue Oct 27, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@patrickhafner
Copy link
Contributor

patrickhafner commented Oct 27, 2024

πŸ“‘ I have found these related issues/pull requests

No.

πŸ›‘οΈ Security Policy

Description

After time changeover a few mins ago, kuma mess up the graph.

Screenshot 2024-10-27 at 02 10 38

πŸ‘Ÿ Reproduction steps

Check your uptime kuma, if you are affected of time changeover from 3am MESZ to 2am again because of change to eu MEZ.

πŸ‘€ Expected behavior

Rewrite graph, maybe delete the first 2AM hour?

πŸ˜“ Actual Behavior

see screenshot

🐻 Uptime-Kuma Version

1.23.15

πŸ’» Operating System and Arch

ubuntu 22.04 docker

🌐 Browser

FF latest

πŸ–₯️ Deployment Environment

  • Runtime: docker (louislam/uptime-kuma:1)
  • Database: sqlite
  • Filesystem used to store the database on: 1
  • number of monitors: 1

πŸ“ Relevant log output

No response

@patrickhafner patrickhafner added the bug Something isn't working label Oct 27, 2024
@patrickhafner
Copy link
Contributor Author

Is this a real bug? I'd love that the community and contributors think about it, because with this change we'll lose a hour of tracking. Otherwise we should extend the graph to show 2am to 3am twice to keep all data.

Looking forward to your input!

@CommanderStorm CommanderStorm changed the title Time changeover in EU is a real mess. summer->winter time changeover looks bad on the graph Oct 27, 2024
@CommanderStorm
Copy link
Collaborator

"Currently" (see #4500) this looks like this

image

Since we don't have a testcase for this, I don't know what the v2.0 system does in this case.

=> what I think is more reasonable is to deal with this at the source and just have a gap for moving foreward and logging twice in the same graph.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants
@patrickhafner @CommanderStorm and others