-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Lens] In-product explanation of how "existing fields" are chosen #83321
Comments
Pinging @elastic/kibana-app (Team:KibanaApp) |
I think we can explain this using a sentence or two. Here's my suggested text, for "available" and "empty":
|
Suggestion: Available fields have data in the first 500 documents that match your filters. To view all fields, expand Empty fields. Some field types cannot be visualized in Lens, including full text and geographic fields. |
I have a few questions/recommendations:
|
@gchaps I think that suggestion makes sense
They don't have to because there is usually a time filter. Not sure we need to say this, but we can.
The text you're suggesting wouldn't be accurate: all we know is that it's empty, we don't know that there are values. |
We have already made some of the proposed changes from the discussion about the confusing behavior of the field list, but are still getting questions about it that could be better answered in product.
I would propose that we make two changes to Lens:
We can say "Available fields have data in the first 500 documents in your results"
The text was updated successfully, but these errors were encountered: