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

[Lens] In-product explanation of how "existing fields" are chosen #83321

Closed
wylieconlon opened this issue Nov 12, 2020 · 5 comments · Fixed by #85544
Closed

[Lens] In-product explanation of how "existing fields" are chosen #83321

wylieconlon opened this issue Nov 12, 2020 · 5 comments · Fixed by #85544
Assignees
Labels
docs enhancement New value added to drive a business result Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@wylieconlon
Copy link
Contributor

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:

  1. Add a tooltip to the "Available fields" and "Empty fields" text to explain how we calculate this:

Screen Shot 2020-11-12 at 12 59 25 PM

We can say "Available fields have data in the first 500 documents in your results"

  1. Add a more descriptive text to the field popover, which is covered in a separate issue
@wylieconlon wylieconlon added Team:Visualizations Visualization editors, elastic-charts and infrastructure Feature:Lens :KibanaApp/fix-it-week labels Nov 12, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@wylieconlon
Copy link
Contributor Author

I think we can explain this using a sentence or two. Here's my suggested text, for "available" and "empty":

Availability is based on the first 500 documents that match your filters. To see all fields, expand the "Empty fields" section. Not all field types can be visualized in Lens, including full text and geographic fields.

These fields did not contain any values in the first 500 documents based on your filters.

cc @KOTungseth @gchaps

@gchaps
Copy link
Contributor

gchaps commented Nov 19, 2020

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.

@wylieconlon wylieconlon added docs enhancement New value added to drive a business result labels Nov 19, 2020
@KOTungseth
Copy link
Contributor

I have a few questions/recommendations:

  • What if users haven't used the filters? Then shouldn't this stop after 500 documents? If so, I'm still wondering where the 500 documents come from. The first 500 documents of what?
  • For the last sentence, could we make it positive? For example, Some field types are unsupported in Lens, including full text and geographic fields.
  • For empty fields, I recommend something like Empty fields include data outside of the first 500 documents.

@wylieconlon
Copy link
Contributor Author

@gchaps I think that suggestion makes sense

@KOTungseth

What if users haven't used the filters?

They don't have to because there is usually a time filter. Not sure we need to say this, but we can.

For empty fields, I recommend something like Empty fields include data outside of the first 500 documents.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs enhancement New value added to drive a business result Feature:Lens Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants