[DOCS] Whats new page for 8.9 #162271
[DOCS] Whats new page for 8.9 #162271
Conversation
amyjtechwriter
added
Team:Docs
Team:Presentation
|
Documentation preview: |
|
Pinging @elastic/kibana-docs (Team:Docs) |
|
Pinging @elastic/kibana-presentation (Team:Presentation) |
|
Pinging @elastic/response-ops (Team:ResponseOps) |
Co-authored-by: István Zoltán Szabó <[email protected]>
Co-authored-by: István Zoltán Szabó <[email protected]>
Co-authored-by: István Zoltán Szabó <[email protected]>
Co-authored-by: István Zoltán Szabó <[email protected]>
Co-authored-by: István Zoltán Szabó <[email protected]>
Co-authored-by: István Zoltán Szabó <[email protected]>
Co-authored-by: István Zoltán Szabó <[email protected]>
|
Looks like this enhancement did not make the list #156618 |
There was a problem hiding this comment.
Thanks for putting this together, @amyjtechwriter.
Can you work with @nreese to ensure his item gets added before the 8.9 release?
I also left some less-pressing feedback that you can address after the release. I'd like you to work with @gchaps and @szabosteve to rework these docs so they look more like ones we've had in previous releases.
Thanks again!
|
|
||
| [discrete] | ||
| ==== Wildcard search in dashboard controls | ||
| **Dashboard** now supports searching for strings that are found within the values shown in a control. Previously, it was required for the string to be located at the start of the value in order to be found. However this is a more expensive option then just searching for the prefix, so it’s disabled by default. To enable it in **Dashboard** select Edit control > Options list settings > Contains. |
There was a problem hiding this comment.
This paragraph could use a rewrite. For example, we could rephrase:
Dashboard now supports searching for strings that are found within the values shown in a control.
to something like:
You can now search for strings anywhere within a control.
We should almost never use phrases like "in order to".
| [discrete] | ||
| ==== Stacked bar chart legend | ||
|
|
||
| The order of stacked bar chart legends is now based on popularity with the most important element displayed on top. You no longer need to scroll to the bottom of the legend to find the most popular data in the chart. |
There was a problem hiding this comment.
The order of stacked bar chart legends is now based on popularity with the most important element displayed on top.
"Popularity" seems like odd phrasing here. We're basically saying "ranked by value in descending order."
Instead of "most popular element," I think it's more accurate to say the "segment with the highest total value."
You no longer need to scroll to the bottom of the legend to find the most popular data in the chart.
Do we need this sentence?
| Previously: | ||
| [role="screenshot"] | ||
| image::images/oldwayhighlighted.png[Example of the old ordering of the chart legend, width=80%] | ||
|
|
||
| New in 8.9: | ||
| [role="screenshot"] | ||
| image::images/newwayhighlighted.png[Example of the new ordering of the chart legend, width=80%] |
There was a problem hiding this comment.
We should avoid using phrases with colons to set off images. Generally, we treat images as "enriching but optional." In this case, I'd only include a screenshot of the new image.
We may also want to crop the photo so the legend is more in focus. It's difficult to read right now.
| [discrete] | ||
| ==== Step curve | ||
|
|
||
| **Lens** now supports three new options for line charts. The three options are straight, smooth, and step. Step curve line charts help users see clearly when data changes at irregular intervals, which helps to avoid misinterpretation. When creating visualizations select **Line** in the visualization type dropdown. Then use the visual options menu to choose between straight, smooth, or step in the Line interpolation dropdown. |
There was a problem hiding this comment.
This also needs a rewrite. We should call this out as a line interpolation option. I'm also not sure why we're mentioning in the existing "straight" or "smooth" options.
| [discrete] | ||
| ==== Significance (significant terms) | ||
|
|
||
| This new ranking method in the top values breakdown displays data by significance (significant terms). It permits us to get the terms that are important and likely the most critical for a given query. It’s a powerful way to find anomalies in your data with multiple use cases. Read more {ref}/search-aggregations-bucket-significantterms-aggregation.html[here]. |
There was a problem hiding this comment.
It permits us to get the terms that are important and likely the most critical for a given query.
Unless providing a recommendation, avoid first person in the docs. In this case, "us" refers to the user should you should use "you" (second person).
| ==== Significance (significant terms) | ||
|
|
||
| This new ranking method in the top values breakdown displays data by significance (significant terms). It permits us to get the terms that are important and likely the most critical for a given query. It’s a powerful way to find anomalies in your data with multiple use cases. Read more {ref}/search-aggregations-bucket-significantterms-aggregation.html[here]. | ||
| This is not just based on the most popular terms in a set. When calculating significant terms, Elasticsearch looks for significant changes in popularity of a specific term between two sets of data. A foreground set (the data returned by a query) and a background set (the data in our indices). This is supported on all charts. |
| [role="screenshot"] | ||
| image::images/annotation.gif[Example of how to save an annotation group to the visualize library] |
There was a problem hiding this comment.
Can we bump up the size of the GIF here? It's hard for me to see?
|
|
||
| You can now create a word cloud in **Lens** using Tag cloud, which is currently in technical preview. When creating new visualizations, select **Tag cloud** in the visualization type dropdown. From the available fields drag and drop the desired field into the workspace to visualize keywords. |
There was a problem hiding this comment.
For items in technical preview, we should include a preview:[] admonition, similar to the ML one below.
## Summary Adding spatial join information to the whats new page for 8.9 Relates to: #162271 --------- Co-authored-by: István Zoltán Szabó <[email protected]>
## Summary Corrections to the [Whats new page for 8.9](https://www.elastic.co/guide/en/kibana/8.9/whats-new.html). Original PR [here](#162271) with the actionable feedback. Closes:[ #150](https://github.com/orgs/elastic/projects/1232/views/4?pane=issue&itemId=35566282)
This PR adds details about whats new to the 8.9 release on the whats new page: https://www.elastic.co/guide/en/kibana/8.9/whats-new.html