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] [Docs] Add more QA for Lens #97142

Merged
merged 25 commits into from
May 31, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
25 commits
Select commit Hold shift + click to select a range
138e63b
:memo: Add more QA for Lens
dej611 Apr 14, 2021
0b29dbf
:fire: Remove duplicate
dej611 Apr 14, 2021
460489d
Update docs/user/dashboard/lens.asciidoc
dej611 Apr 27, 2021
971ea11
Update docs/user/dashboard/lens.asciidoc
dej611 Apr 27, 2021
f472ab2
Update docs/user/dashboard/lens.asciidoc
dej611 Apr 28, 2021
20470e8
:memo: Fix few issues based on feedback + new faq
dej611 Apr 28, 2021
c65265c
:camera: Add missing picture
dej611 Apr 28, 2021
876116e
Update docs/user/dashboard/lens.asciidoc
dej611 May 5, 2021
691b061
Update docs/user/dashboard/lens.asciidoc
dej611 May 5, 2021
7db8640
Update docs/user/dashboard/lens.asciidoc
dej611 May 5, 2021
2cbf9ef
Update docs/user/dashboard/lens.asciidoc
dej611 May 5, 2021
0aa77f4
Update docs/user/dashboard/lens.asciidoc
dej611 May 5, 2021
d80ef91
Update docs/user/dashboard/lens.asciidoc
dej611 May 5, 2021
e4f9717
Update docs/user/dashboard/lens.asciidoc
dej611 May 5, 2021
bf4db3d
Update docs/user/dashboard/lens.asciidoc
dej611 May 6, 2021
634d6ce
Update docs/user/dashboard/lens.asciidoc
dej611 May 6, 2021
062319d
Update docs/user/dashboard/lens.asciidoc
dej611 May 6, 2021
444d2f7
Update docs/user/dashboard/lens.asciidoc
dej611 May 6, 2021
c8d901e
Update docs/user/dashboard/lens.asciidoc
dej611 May 6, 2021
36e0619
Update docs/user/dashboard/lens.asciidoc
dej611 May 6, 2021
088a107
Update docs/user/dashboard/lens.asciidoc
dej611 May 6, 2021
9c4f409
Update docs/user/dashboard/lens.asciidoc
dej611 May 6, 2021
5e4a260
:ok_hand: Integrated feedback
dej611 May 14, 2021
8ad9cd4
:ok_hand: More feedback
dej611 May 14, 2021
af21cc0
Merge branch 'master' into fix/more-lens-faq
kibanamachine May 26, 2021
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
49 changes: 49 additions & 0 deletions docs/user/dashboard/lens.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -179,6 +179,8 @@ A subset of *Lens* visualizations support value labels.
[role="screenshot"]
image::images/lens_value_labels_xychart_toggle.png[Lens Bar chart value labels menu]

NOTE: In bar charts, you are unable to move the label positions.

* *Pie*, *Donut*, and *Treemap*
+
[role="screenshot"]
Expand Down Expand Up @@ -232,6 +234,9 @@ refer to <<explore-fields-in-your-data,Explore the fields in your data>>.

Sorting dimensions in visualizations is unsupported in *Lens*.

You can sort the dimensions for a single column in data tables: click the column header, then select the sorting criteria you want to use.
If you use the dimension as `Columns`, then all the columns that belong to the same dimension are sorted in the table.

[float]
[[is-it-possible-to-use-saved-serches-in-lens]]
===== How do I visualize saved searches?
Expand All @@ -243,3 +248,47 @@ Visualizing saved searches in unsupported in *Lens*.
===== How do I change the number of suggestions?

Configuring the *Suggestions* that *Lens* automatically populates is unsupported.

[float]
[[is-it-possible-to-use-different-indexpatterns-in-lens]]
===== Can I visualize multiple index patterns in a single visualization?

You can create *Bar*, *Line* and *Area* charts from multiple index patterns.

Each *Layer* in a visualization is associated with an index pattern and mutiple *Layers* can be combined together within the same visualization. Each *Layer* also has a chart switcher button in order to select the best type of visualization for the specific dataset.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Each *Layer* in a visualization is associated with an index pattern and mutiple *Layers* can be combined together within the same visualization. Each *Layer* also has a chart switcher button in order to select the best type of visualization for the specific dataset.
Each chart *Layer* is associated with an index pattern, and you can combine multiple *Layers* in the same chart. Each *Layer* also has a menu to change the visualization type, which allows you to select the best type of visualization for the data.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this section is about using multiple index patterns, is this sentence necessary?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that, while it may sounds a distinct issue, there is often a correlation between overlaying different charts types from different index patterns.

You can also change the index pattern for a single *Layer*.

[float]
[[why-my-field-x-is-missing-from-the-fields-list]]
===== Why is my field X missing from the fields list?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are a few possible reasons for a field to be missing:

  • Full text
  • Geo (in all released versions)
  • Mapping is not supported by index patterns, like flattened or object

Also, sometimes user say "missing" when it's actually in the "empty" list. Would be nice to summarize all of these if it can be done concisely, but I don't think it's a blocker.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. I'll merge this and revisit that particular section in a subsequent PR


*Lens* does not support the visualization of full-text fields, therefore it is not showing them in the data summary.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
*Lens* does not support the visualization of full-text fields, therefore it is not showing them in the data summary.
Creating visualizations with full-text fields is unsupported in *Lens*. When your index pattern contains a full-text field, *Lens* displays the `X.keyword` field, but is unable to display the data summary.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the suggested version is not correct, as it assumes always the availability of the X.keyword field for each full-text field, while this is not true.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about:

Creating visualizations with full-text fields is unsupported in Lens. When your index pattern contains full-text fields, the fields do not appear in the data summaries.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The bits of information to communicate, I think, are the following three:

  • Lens does not support full-text fields
  • If a full-text field has also keyword subfield then the latter is shown
  • Data summaries are not available for full-text fields, even when the keyword subfield is available.

In particular the first 2 are the most important part, while the third could be omitted if we want - it's just nice as it adds an extra bit to the essential information.


[float]
[[how-to-handle-gaps-in-time-series-visualizations]]
===== How do I handle gaps in time series visualizations?

*Lens* provides a set of features to handle missing values for *Area* and *Line* charts, which is useful for sparse data in time series data.

To select a different way to represent missing values, open the *Visual options* menu, then select how to handle missing values. The default is to hide the missing values.
+
[role="screenshot"]
image::images/lens_missing_values_strategy.png[Lens Missing values strategies menu]

[float]
[[is-it-possible-to-change-the-scale-of-Y-axis]]
===== Is it possible to statically define the scale of the y-axis in a visualization?

The ability to start the y-axis from another value than 0, or use a logarithmic scale, is unsupported in *Lens*.

[float]
[[is-it-possible-to-have-pagination-for-datatable]]
===== Is it possible to have pagination in a data table?

Pagination in a data table is unsupported in *Lens*. However, the <<types-of-visualizations,aggregation-based data table>> supports pagination.

[float]
[[is-it-possible-to-have-more-than-one-Y-axis-scale]]
===== Is it possible to have more than one y-axis scale in visualizations?

*Lens* lets you pick, for each Y dimension, up to two distinct axis: *left* and *right*. Each axis can have a different scale.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
*Lens* lets you pick, for each Y dimension, up to two distinct axis: *left* and *right*. Each axis can have a different scale.
For each y-axis in the editor, *Lens* supports *left* and *right* axes. Each axis can have a different scale.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For each y-axis in the editor

It does not sound not to immediate to me exactly what it meant.