[GH-ISSUE #350] TimeZone #270

Closed
opened 2026-02-25 23:41:50 +03:00 by kerem · 9 comments
Owner

Originally created by @Rustymage on GitHub (Apr 1, 2020).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/350

Morning,

Maybe I'm being slightly dense but my timezone is now an hour out and it's causing my notifications to continually trigger.

I'm in the London BST timezone using docker to run the Healthchecks container.

How can I update my timezone or setup my system to not trigger the alerts when the timezones from container to running check do not line up?

Thanks in advance :)

Originally created by @Rustymage on GitHub (Apr 1, 2020). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/350 Morning, Maybe I'm being slightly dense but my timezone is now an hour out and it's causing my notifications to continually trigger. I'm in the London BST timezone using docker to run the Healthchecks container. How can I update my timezone or setup my system to not trigger the alerts when the timezones from container to running check do not line up? Thanks in advance :)
kerem closed this issue 2026-02-25 23:41:50 +03:00
Author
Owner

@cuu508 commented on GitHub (Apr 1, 2020):

Hi @Rustymage, make sure the timezone for individual checks match the timezone on your monitored systems.

You can see and change the timezone in check details page:

image

Also related: https://healthchecks.io/faq/#timezones

<!-- gh-comment-id:607082155 --> @cuu508 commented on GitHub (Apr 1, 2020): Hi @Rustymage, make sure the timezone for individual checks match the timezone on your monitored systems. You can see and change the timezone in check details page: ![image](https://user-images.githubusercontent.com/661859/78110157-30c28600-7403-11ea-9c89-34dfa11927b7.png) Also related: https://healthchecks.io/faq/#timezones
Author
Owner

@Rustymage commented on GitHub (Apr 1, 2020):

As an example:

  • My server cron is setup to backup and ping Healthchecks at 0120 (GMT BST), it does this successfully

  • My Healthchecks cron job is awaiting a ping at 0120 (Europe/London) with a grace time of 60 minutes, the timestamp on the ping from the server is 2020-04-01T01:20:00.491177+00:00

  • The Healthchecks container sends out an alert at 0120, clearly just before the server pings it

The date on my server is: Wed 1 Apr 08:48:07 BST 2020
The date on the Healthchecks container is: Wed Apr 1 07:48:29 UTC 2020

Is it recommended to restart the container and server?

<!-- gh-comment-id:607091893 --> @Rustymage commented on GitHub (Apr 1, 2020): As an example: - My **server** cron is setup to backup and ping Healthchecks at `0120` (GMT BST), it does this successfully - My _Healthchecks_ cron job is awaiting a ping at `0120` (Europe/London) with a grace time of 60 minutes, the timestamp on the ping from the **server** is `2020-04-01T01:20:00.491177+00:00` - The Healthchecks container sends out an alert at `0120`, clearly just before the **server** pings it The date on my **server** is: `Wed 1 Apr 08:48:07 BST 2020` The date on the _Healthchecks_ container is: `Wed Apr 1 07:48:29 UTC 2020` Is it recommended to restart the container and server?
Author
Owner

@cuu508 commented on GitHub (Apr 1, 2020):

What is the configured timezone for the specific check – what do you see in the "Check Details" page?

Could you post a screenshot of the check details page, with the "Schedule" and "Log" sections visible, and any sensitive bits edited out?

<!-- gh-comment-id:607112564 --> @cuu508 commented on GitHub (Apr 1, 2020): What is the configured timezone for the specific check – what do you see in the "Check Details" page? Could you post a screenshot of the check details page, with the "Schedule" and "Log" sections visible, and any sensitive bits edited out?
Author
Owner

@Rustymage commented on GitHub (Apr 1, 2020):

Screenshot 2020-04-01 at 16 57 05 Screenshot 2020-04-01 at 16 58 24
<!-- gh-comment-id:607337318 --> @Rustymage commented on GitHub (Apr 1, 2020): <img width="1367" alt="Screenshot 2020-04-01 at 16 57 05" src="https://user-images.githubusercontent.com/19926955/78159231-338c9d80-743a-11ea-928a-631e01fc05a4.png"> <img width="1354" alt="Screenshot 2020-04-01 at 16 58 24" src="https://user-images.githubusercontent.com/19926955/78159243-36878e00-743a-11ea-95fe-119fc6ad6a90.png">
Author
Owner

@cuu508 commented on GitHub (Apr 1, 2020):

Thanks for posting the screenshots!

To me it looks like the pings from last few days are sent an hour late. The ping is expected at 3:00 BST, which is 2:00 UTC. Instead in the log we see it arrives at 3:00 UTC.

What are you using to schedule the daily runs? If it's cron, have you by any chance changed server's timezone recently? cron daemon may need to be restarted to pick up the timezone change.

<!-- gh-comment-id:607442616 --> @cuu508 commented on GitHub (Apr 1, 2020): Thanks for posting the screenshots! To me it looks like the pings from last few days are sent an hour late. The ping is expected at 3:00 BST, which is 2:00 UTC. Instead in the log we see it arrives at 3:00 UTC. What are you using to schedule the daily runs? If it's cron, have you by any chance changed server's timezone recently? cron daemon may need to be restarted to pick up the timezone change.
Author
Owner

@Rustymage commented on GitHub (Apr 1, 2020):

The timezone has auto changed when I entered BST. I'll restart and check back.

Cheers

<!-- gh-comment-id:607443350 --> @Rustymage commented on GitHub (Apr 1, 2020): The timezone has auto changed when I entered BST. I'll restart and check back. Cheers
Author
Owner

@cuu508 commented on GitHub (Apr 1, 2020):

If the server has systemd, what's the output of timedatectl status and what is in your /etc/timezone? Are you using cron as the scheduler?

<!-- gh-comment-id:607446296 --> @cuu508 commented on GitHub (Apr 1, 2020): If the server has systemd, what's the output of `timedatectl status` and what is in your `/etc/timezone`? Are you using cron as the scheduler?
Author
Owner

@Rustymage commented on GitHub (Apr 2, 2020):

So I found the issue. It was a container with the incorrect time. Thanks for the assistance. I learnt to triple check containers :)

<!-- gh-comment-id:608079480 --> @Rustymage commented on GitHub (Apr 2, 2020): So I found the issue. It was a container with the incorrect time. Thanks for the assistance. I learnt to triple check containers :)
Author
Owner

@cuu508 commented on GitHub (Apr 6, 2020):

Thanks, good to hear you tracked down the issue!

<!-- gh-comment-id:609675932 --> @cuu508 commented on GitHub (Apr 6, 2020): Thanks, good to hear you tracked down the issue!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/healthchecks#270
No description provided.