Strange problem, which I’ve only noticed since upgrading to 4.4.1 on a test box.
I wanted to see if others noticed the same, or if it’s something I’ve missed, before I log a bug on github.
Using a single CentOS 7 dev/test server, and my own workstation (Windows).
Installed influxDB and/or Prometheus (just tried both to rule out datasource issues in any way - unlikely as I thought it’d be).
Metrics are going in fine, and are displaying correctly on panels.
The first time I notice the problem is when I configured alerts inside Grafana.
The moment I saved and activated the alert, it says “Pending for in an hour”.
I realised this was a little odd and began to dig, thinking the time sources on the server must be out or something.
Both my workstation and the server are reporting that they are synced up and the correct times (BST timezone).
Despite this, the dashboards seem to believe they are an hour ahead, no matter what.
Each time the alert status changes, it says “for in an hour”.
If I check the dashboard metadata, it too says the last modified time is an hour ahead of the actual time.
Panels are plotting at the correct times on histrogram X axis.
I’ve tried changing the dashboards timezone to UTC, local browser and default (presumably server time?) - None of which change the situation.
Checked through configuration, can’t see any timezone settings towards Grafana.
Am I missing something? Has anyone else noted this? Is there anything I can do, before/aside from logging a bug?