Project

General

Profile

Actions

Bug #25499

closed

Event log table default period of two hours is too short

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

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
It bothers me each time
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
87
Name check:
To do
Fix check:
Checked
Regression:
No

Description

When visiting the event logs page, the data fetched for the table is the data for the last 2 hours (set in #24502).

We should set the period at 2 DAYS for event logs, and keep it at 2 hours by default for other tables : technical logs, etc.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #24502: Technical logs are not loaded when visiting the tabReleasedVincent MEMBRÉActions
Actions #1

Updated by Clark ANDRIANASOLO 3 months ago

  • Related to Bug #24502: Technical logs are not loaded when visiting the tab added
Actions #2

Updated by Clark ANDRIANASOLO 3 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Clark ANDRIANASOLO to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/5890
Actions #3

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.1.7 to 8.1.8
Actions #4

Updated by Clark ANDRIANASOLO 3 months ago

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

Updated by Alexis Mousset about 1 month ago

  • Priority changed from 88 to 87
  • Fix check changed from To do to Checked
Actions #6

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