Hourly view works correctly:

vs
Minute view is completely empty:

SQL is also having all minutly data there:
mysql> SELECT * from metric_points where metric_id = 1;
+-----+-----------+-----------+---------+---------------------+---------------------+
| id | metric_id | value | counter | created_at | updated_at |
+-----+-----------+-----------+---------+---------------------+---------------------+
| 4 | 1 | 24690.155 | 1 | 2018-06-23 08:54:02 | 2018-06-23 08:54:02 |
| 9 | 1 | 24690.155 | 1 | 2018-06-23 08:55:02 | 2018-06-23 08:55:02 |
| 22 | 1 | 24690.155 | 1 | 2018-06-23 08:56:02 | 2018-06-23 08:56:02 |
| 28 | 1 | 24690.155 | 1 | 2018-06-23 08:57:02 | 2018-06-23 08:57:02 |
| 33 | 1 | 18070.634 | 1 | 2018-06-23 08:58:02 | 2018-06-23 08:58:02 |
| 48 | 1 | 11465.148 | 1 | 2018-06-23 08:59:02 | 2018-06-23 08:59:02 |
| 50 | 1 | 12616.071 | 1 | 2018-06-23 09:00:02 | 2018-06-23 09:00:02 |
| 59 | 1 | 12616.071 | 1 | 2018-06-23 09:01:01 | 2018-06-23 09:01:01 |
| 68 | 1 | 12616.071 | 1 | 2018-06-23 09:02:01 | 2018-06-23 09:02:01 |
| 74 | 1 | 12616.071 | 1 | 2018-06-23 09:03:01 | 2018-06-23 09:03:01 |
| 81 | 1 | 12616.071 | 1 | 2018-06-23 09:04:01 | 2018-06-23 09:04:01 |
| 94 | 1 | 12616.071 | 1 | 2018-06-23 09:05:01 | 2018-06-23 09:05:01 |
| 98 | 1 | 12616.071 | 1 | 2018-06-23 09:06:01 | 2018-06-23 09:06:01 |
| 108 | 1 | 14177.494 | 1 | 2018-06-23 09:07:01 | 2018-06-23 09:07:01 |
+-----+-----------+-----------+---------+---------------------+---------------------+
14 rows in set (0.00 sec)
:wave: Thank you for opening your first issue. I'm just an automated bot that's here to help you get the information you need quicker, so please ignore this message if it doesn't apply to your issue.
If you're looking for support, you should try the Slack group by registering your email address at https://cachethq-slack.herokuapp.com. Alternatively, email [email protected] for our Professional support service (please note, this a paid service.
If you're issue is with documentation, you can suggest edits by clicking the Suggest Edits link on any page, or open an issue at https://github.com/CachetHQ/Docs
Thanks for reporting! As you can see, there are a lot of Metrics issues currently open, metrics suck currently 馃槵
Unfortunately that's the only reason why I use this tooling - to track our metrics 馃
Oh well seems like our metrics classes need a huge refactoring!
Thank your for your quick answer! Looking forward!
I will get this fixed ASAP :)
Now that I've got a theming system on the go (ready for the next re-design) I'll start looking at Metrics next. I've got a whole bunch of issues to work through https://github.com/CachetHQ/Cachet/labels/Metrics
having almost the exact same issue, only for me it isn't completely blank, it shows the last 2 datapoints only

Weirdly I don't have any Last Hour points, and my data shows that the created_at is following GMT, where my updated_at is GMT+2 (which is correct).
MariaDB [cachet]> select * from metric_points;
+----+-----------+--------+---------+---------------------+---------------------+
| id | metric_id | value | counter | created_at | updated_at |
+----+-----------+--------+---------+---------------------+---------------------+
| 1 | 2 | 16.300 | 1 | 2019-09-09 13:12:00 | 2019-09-09 15:11:55 |
| 2 | 2 | 16.300 | 1 | 2019-09-09 13:13:30 | 2019-09-09 15:13:42 |
| 3 | 2 | 16.300 | 1 | 2019-09-09 13:15:30 | 2019-09-09 15:15:28 |
| 4 | 2 | 16.300 | 1 | 2019-09-09 13:17:00 | 2019-09-09 15:17:00 |
| 5 | 2 | 16.000 | 1 | 2019-09-09 13:17:30 | 2019-09-09 15:17:18 |
| 6 | 2 | 16.000 | 1 | 2019-09-09 13:20:30 | 2019-09-09 15:20:31 |
| 7 | 2 | 16.300 | 1 | 2019-09-09 13:24:00 | 2019-09-09 15:24:01 |
| 8 | 2 | 16.300 | 1 | 2019-09-09 13:31:30 | 2019-09-09 15:31:29 |
| 9 | 2 | 16.300 | 1 | 2019-09-09 13:37:30 | 2019-09-09 15:37:30 |
| 10 | 2 | 16.300 | 1 | 2019-09-09 13:43:00 | 2019-09-09 15:42:51 |
| 11 | 2 | 16.300 | 1 | 2019-09-09 13:43:00 | 2019-09-09 15:43:08 |
| 12 | 2 | 16.000 | 1 | 2019-09-09 14:08:30 | 2019-09-09 16:08:36 |
| 13 | 2 | 16.100 | 1 | 2019-09-09 14:13:30 | 2019-09-09 16:13:26 |
| 14 | 2 | 16.100 | 1 | 2019-09-09 14:16:30 | 2019-09-09 16:16:16 |
| 15 | 2 | 16.200 | 1 | 2019-09-09 14:17:00 | 2019-09-09 16:17:01 |
| 16 | 2 | 16.200 | 1 | 2019-09-09 14:20:00 | 2019-09-09 16:20:01 |
| 17 | 2 | 16.100 | 1 | 2019-09-09 14:25:00 | 2019-09-09 16:25:01 |
| 18 | 2 | 16.100 | 1 | 2019-09-09 14:30:00 | 2019-09-09 16:30:02 |
| 19 | 2 | 16.300 | 1 | 2019-09-09 14:34:00 | 2019-09-09 16:34:38 |
| 20 | 2 | 16.300 | 1 | 2019-09-09 14:35:00 | 2019-09-09 16:35:01 |
| 21 | 2 | 16.300 | 1 | 2019-09-09 14:34:00 | 2019-09-09 16:35:07 |
| 22 | 2 | 16.300 | 1 | 2019-09-09 14:35:00 | 2019-09-09 16:35:13 |
| 23 | 2 | 16.100 | 1 | 2019-09-09 14:35:30 | 2019-09-09 16:35:41 |
| 24 | 2 | 16.200 | 1 | 2019-09-09 14:45:00 | 2019-09-09 16:45:01 |
| 25 | 2 | 16.200 | 1 | 2019-09-09 14:50:00 | 2019-09-09 16:50:02 |
| 26 | 2 | 16.400 | 1 | 2019-09-09 14:55:00 | 2019-09-09 16:55:01 |
| 27 | 2 | 16.400 | 1 | 2019-09-09 14:55:50 | 2019-09-09 16:55:50 |
+----+-----------+--------+---------+---------------------+---------------------+
27 rows in set (0.00 sec)
PHP Timezone and MySQL timezone is correct as well as the Timezone set in Cachet.
Anyone know why?
Most helpful comment
I will get this fixed ASAP :)