Project

General

Profile

Actions

Bug #25720

closed

Technical and event logs get log from browser timezone instead of server timezone

Added by Clark ANDRIANASOLO about 2 months ago. Updated about 1 month ago.

Status:
Released
Priority:
1 (highest)
Category:
Web - Maintenance
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
It bothers me each time
User visibility:
First impressions of Rudder
Effort required:
Small
Priority:
108
Name check:
To do
Fix check:
Checked
Regression:
No

Description

In a node details page, the "Technical logs" tab is initialized with the last 1000 server logs, it works fine until we get logs from specific dates : the default start and end dates are one computed with the timezone of the browser (and are displayed without any timezone information), but when getting logs, the returned table shows elements from the same time as queried but with the server timezone.
This is misleading when the user timezone is different from the browser timezone : my server is on the UTC+3 timezone, but my browser is on the UTC+2 timezone, and the default time is therefore one hour behind when opening the technical logs tabs, when I click on the "Get logs" right when arriving on the page.

When I arrive on the page :

But I get data before 14:40:00+0300 when I click on the button.

Also, when I refresh the table after changing the start and end times and getting logs, the table displays the last 1000 server logs back.

The same happens in the event logs page.

The default dates should either always be on the server timezone or the displayed information in the tables in the browser timezone.


Files

clipboard-202410231441-dgu3j.png (61.3 KB) clipboard-202410231441-dgu3j.png Clark ANDRIANASOLO, 2024-10-23 14:41
Actions #1

Updated by Clark ANDRIANASOLO about 2 months ago

  • Description updated (diff)
Actions #2

Updated by François ARMAND about 2 months ago

  • Category set to Web - Maintenance
  • Priority changed from To review to 1 (highest)
Actions #3

Updated by François ARMAND about 2 months ago

  • Assignee set to Clark ANDRIANASOLO
Actions #4

Updated by Clark ANDRIANASOLO about 2 months ago

  • Status changed from New to In progress
Actions #5

Updated by Clark ANDRIANASOLO about 2 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Clark ANDRIANASOLO to Raphael GAUTHIER
  • Pull Request set to https://github.com/Normation/rudder/pull/5963
Actions #6

Updated by Clark ANDRIANASOLO about 1 month ago

  • Status changed from Pending technical review to Pending release
Actions #7

Updated by Félix DALLIDET about 1 month ago

  • Fix check changed from To do to Checked
Actions #8

Updated by Vincent MEMBRÉ about 1 month ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 8.1.8 and 8.2.1 which were released today.

Actions

Also available in: Atom PDF