Aggregation timestamp reverts to UTC although "timestamp" field is UTC+1

1. Describe your incident:

I’ve configured time settings to UTC+1 and everything has been to my satisfaction. But yesterday I created an aggregation using the metric"timestamp(latest value)" and in that aggregation the timestamp is shown as UTC. See screenshot. Is this a bug or do I need to configure time somewhere else as well?

2. Describe your environment:

  • OS Information:
    FreeBSD 13
  • Package Version:
    Graylog 5.0.5
    Elasticsearch 7.10.1

I’m guessing your logged in as admin, what happens if you run the same widget when logged in as another user and play around with the settings for that users timezone?

I created a new user. The timestamps in message fields change when specifying other time zones, but the red circled one remains 19.06 no matter what (for the message in question above).

Just to be extra clear, the time displayed for “Graylog server” in the Overview-Time Configuration, whether logged in as admin or another user, is always UTC+1, but the metric timestamp(latest) will display UTC.

So I havent been able to confirm, but I am wondering if you might be dealing with this bug that was just opened the other day, where at least one of the apis is ignoring timezone `/api/views/search/messages` does not obey `time_zone` argument, always returns UTC · Issue #15030 · Graylog2/graylog2-server · GitHub

I will add your post to the issue so that the devs can see if they are related.

thanks for doing that!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.