If searched with Absolute Time range (ex for the last hour) - it works correctly, the record is returned.
But not when the Relative (the default) “Search in the last 1 hour” option is selected !
Check your real date in graylog server, in the past i have similar problem, and graylog web shows correct time in settings, but in reality server time was off.
I use Graylog 3.3.2, have left the Graylog server’s timestamp in its default - UTC, and not set it to my (Tirana) timezone.
I did this because of what I read in note (above) “Time Zone Delay”:
“Ensure all your servers timezones are set to UTC (even if they don’t live in UTC), then all your timestamps arrive in UTC.”
and I did changed the root_timezone at server.conf from UTC to Europe/Tirane. I restarted the server but on the “Overview” dashboard the Graylog server timezone still persisted to +00:00.
can you advise on how to set the root_timezone?
best regards
Altin
ps. what it is meant by “real date in graylog server” ?
I did changed the Ubuntu’s (ova) OS timezone from UTC to Europe/Tirana.
This changed the local time clock + 2 hours.
I can set it with timedatectl - but it is reset again on every restart.
In my graylog installation I see timedatectl and graylog’s identical.
sudo timedatectl set-timezone YOUR_TIMEZONE should definitely make it permanent. Please restart graylog-server and elasticsearch services after change, or reboot.
root_timezone is settings only for user admin (to render correct admin user timezone), if you use it to login to web interface, it’s not used by graylog server. Another users use timezone from user profile.
root_timezone at server.conf should be left default (commented) UTC.
The OS timezone and datetime must be set according to local settings
The user’s (<>admin) timezone must be set must be set according to local settings
When on Oracle VM - check `Hardware clock in UTC Time