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
As a solution, we can reuse our current date picker which we are using on the search page. It has a lot of advantages.
has 3 types of time ranges (relative, absolute, keyword)
has presets
all users are familiar with that
The main issue we might face here is that not all entity data table endpoints accept different time range types. To solve this problem we can:
Before sending data to BE, convert the time range to absolute
extend endpoints
remove some of the time range types ( most likely the biggest problem might be with keyword )
Why?
In the entity data table, we have a very simple date picker where the user has to type time ranges. That might not be comfortable if the user wants to work fast and choose a relative time range.
Your Environment
Graylog Version:
OpenSearch Version:
MongoDB Version:
Operating System:
Browser version:
The text was updated successfully, but these errors were encountered:
What?
As a solution, we can reuse our current date picker which we are using on the search page. It has a lot of advantages.
The main issue we might face here is that not all entity data table endpoints accept different time range types. To solve this problem we can:
Why?
In the entity data table, we have a very simple date picker where the user has to type time ranges. That might not be comfortable if the user wants to work fast and choose a relative time range.
Your Environment
The text was updated successfully, but these errors were encountered: