Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add info message to Search page when querying Warm Tier data #21094

Open
williamtrelawny opened this issue Dec 2, 2024 · 1 comment
Open
Labels

Comments

@williamtrelawny
Copy link
Contributor

What?

Searches should include the same Info message that Widgets do when querying Warm Tier data:
Image

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:
Image

First, this information is hidden behind the same warning button used for search query errors, which is unexpected:
Image

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?

  1. 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
@kmerz
Copy link
Member

kmerz commented Dec 3, 2024

For me, that is a bug and should be fixed. This is not a feature request. Thanks for reporting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants