You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changing the relative search value to a number between 1 and 44 works fine, 45 and 59 minutes causes the From: displayed to round up to From: an hour ago, between 61 and 89 minutes, round down to From:an hour ago, from 90 to 119 to round up to From: 2 hours ago, and trying to type 120 minutes. It automatically changes the unit from minutes to hours and changes the number to a 2.
Expected Behavior
The displayed time should accurately reflect the configured time
Current Behavior
certain time frames round up or down and do not reflect the configured time accurately. Some change the units as well.
Possible Solution
change the behavior to accurately reflect the configured relative time range
Steps to Reproduce (for bugs)
See description above
Context
Your Environment
Graylog Version: 4.1.1+27dec96
Java Version: 1.8.0_292
Elasticsearch Version: 6.8.14
MongoDB Version: 4.4.6
Operating System: CentOS 7
Browser version: Edge Chromium 92 and Firefox 90
The text was updated successfully, but these errors were encountered:
Changing the relative search value to a number between 1 and 44 works fine, 45 and 59 minutes causes the From: displayed to round up to From: an hour ago, between 61 and 89 minutes, round down to From:an hour ago, from 90 to 119 to round up to From: 2 hours ago, and trying to type 120 minutes. It automatically changes the unit from minutes to hours and changes the number to a 2.
Expected Behavior
The displayed time should accurately reflect the configured time
Current Behavior
certain time frames round up or down and do not reflect the configured time accurately. Some change the units as well.
Possible Solution
change the behavior to accurately reflect the configured relative time range
Steps to Reproduce (for bugs)
See description above
Context
Your Environment
The text was updated successfully, but these errors were encountered: