Timestamp in Dashboard are always "current time"

[Damiano]

Hi all, I’m facing a new problem on my fresh Graylog installation:

Environment:
Centos 7.6
Graylog 3.0.1
Elasticsearch 6.7.1
MongoDB v4.0.9

It seems that all my configured Dashboards are showing as timestamp information the “current time” at the moment when I open the dashboard; on the other hand, I’m receiving the correct timestamps from a numbers of different inputs!
I can see the right timestamp also when I perform queries.

Time configuration in graylog web admin:

User admin: 2019-05-06 17:51:29 +02:00
Your web browser: 2019-05-06 17:51:29 +02:00
Graylog server: 2019-05-06 17:51:29 +02:00

Time configuration on Graylog OS

[root@graylog3 ~]# timedatectl
Local time: Mon 2019-05-06 17:52:13 CEST
Universal time: Mon 2019-05-06 15:52:13 UTC
RTC time: Mon 2019-05-06 15:52:13
Time zone: Europe/Rome (CEST, +0200)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: yes
Last DST change: DST began at
Sun 2019-03-31 01:59:59 CET
Sun 2019-03-31 03:00:00 CEST
Next DST change: DST ends (the clock jumps one hour backwards) at
Sun 2019-10-27 02:59:59 CEST
Sun 2019-10-27 02:00:00 CET

Any Idea about what is wrong in Dashboard configuration?
Thanks a lot

[jan (Jan Doberstein)]

do you might have a screenshot to explain what you describe?

[Damiano]

Sure, I have attached two screenshots;
1] Graylog dashboard explain the issue; I can see only the current time in my dashboard timestamp
2] Graylog query was taken just few seconds after the dashboard screenshot using its query and it shows the right timestamps for all received logs!

[jan (Jan Doberstein)]

ok, just to clarify:

you stacked the date in the quick-values and the timestamp field shows a wrong date in the quick values widget.

Would you mind opening a bug report over at github for that - it looks like a bug to me.

Graylog2/graylog2-server

[Damiano]

Thanks a lot Jan, I opened a bug report in github:
“Timestamp in Dashboard widgets are showing always “current time” #5930”

[jan (Jan Doberstein)]

actually - with 3.1 (released august) that will be possible in the extended search. not sure if the quick values is fixed than.

But extended search will become open source with the same release.