-
Notifications
You must be signed in to change notification settings - Fork 884
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
Better field summaries #1995
Comments
@opensearch-project/opensearch-ux can you check this out? |
|
Is your feature request related to a problem? Please describe.
One of the fundamental tasks in data exploration is understanding the "shape" of the data. Index patterns may have many different fields, and figuring out which fields are interesting, useful, or complete is the first step in separating signal from noise. Field titles and types alone are not sufficient (titles alone may even be misleading, depending on the data source). So
Discover
allows users to click on each field title to see a quick summary:The problem is that, for many fields, these summaries are essentially useless:
Describe the solution you'd like
string
fields, it makes no sense for many other field types (timestamp
, as seen above, or_id
are particularly egregious examples). Instead, we should provide useful summary data. A numerical field summary might include some sort of distribution plot and min, max, median labels. A boolean field might be better summarized with a pie chart.Note that we're also adding similar field summaries to the new visualization creation process, so all of the above (excluding 2) apply equally to that tool.
Describe alternatives you've considered
Most of the above suggestions could be implemented with the same basic UI components, it's just a matter of what information and visualization to put in the popover. But we may also want to explore completely different UI flows for summarizing/inspecting a field, particularly if rethinking the entire Discover experience.
The text was updated successfully, but these errors were encountered: