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.
Situation:
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?
I haven’t explicitly configured a database, so I am presuming sqlite.
Come to think of it, not sure if this is relevant, but I normally install via yum repo however I was being a little hasty and just used the direct aws install method.
As I say, that could be irrelevant but I am just calling out anything that comes to mind.
I’ve just rebuilt it on a completely separate system completely.
Different workstation and server (still Windows/CentOS 7 respectively).
Able to replicate it completely: “ALERTING for in an hour”, despite that the graph panel correctly shows the marker for when it began alerting at the correct time.
Again, I used the main download instead of repo but doubt it makes a difference as I presume it’s just the same binary.
Server/Client times are same, metrics are stored with UTC timestamps.
It is using sqlite and if I open the grafana.db using sqlite3 and do SELECT CURRENT_TIMESTAMP; I am given the UTC timestamp.
I’m based in the UK (BST timezone), so it’s really puzzling me why Grafana is picking up anything to do with a timezone one hour in front for alerting and metadata (last modified dashboard etc).
If required, I can prepare some screen grabs to share?