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
Searches should include the same Info message that Widgets do when querying Warm Tier data:
There already exists in Search a feedback for this actually, but it is overly-verbose, less visible, and in an unintuitive location- behind the Yellow/Warning exclamation mark to the right of the Search bar:
First, this information is hidden behind the same warning button used for search query errors, which is unexpected:
Second, users don't need to know the timestamps listed here, and arguably don't even need to know which Warm Tier Index Sets the search had to query. I think the Blue/Informational message above is sufficient for 95% of users. For the remaining 5%, this information could be retrieved elsewhere and not behind the search query validation error button.
Why?
UX consistency across the product,
Plus the same reasons why it already exists in the Widget view:
2) More useful feedback to user on why search may be taking longer than expected, which reduces frustration and increases patience
3) Reinforces product value by highlighting the Warm Tier functionality of the product and its usefulness, rather than it just being another invisible backend part that users set and forget
Your Environment
Graylog Version: Cloud/6.1
OpenSearch Version: n/a
MongoDB Version: n/a
Operating System: n/a
Browser version: n/a
The text was updated successfully, but these errors were encountered:
What?
Searches should include the same Info message that Widgets do when querying Warm Tier data:
There already exists in Search a feedback for this actually, but it is overly-verbose, less visible, and in an unintuitive location- behind the Yellow/Warning exclamation mark to the right of the Search bar:
First, this information is hidden behind the same warning button used for search query errors, which is unexpected:
Second, users don't need to know the timestamps listed here, and arguably don't even need to know which Warm Tier Index Sets the search had to query. I think the Blue/Informational message above is sufficient for 95% of users. For the remaining 5%, this information could be retrieved elsewhere and not behind the search query validation error button.
Why?
Plus the same reasons why it already exists in the Widget view:
2) More useful feedback to user on why search may be taking longer than expected, which reduces frustration and increases patience
3) Reinforces product value by highlighting the Warm Tier functionality of the product and its usefulness, rather than it just being another invisible backend part that users set and forget
Your Environment
The text was updated successfully, but these errors were encountered: