[DOCS] Refresh transform screenshots with histograms (#59264) (#60145)

This commit is contained in:
Lisa Cawley 2020-07-23 11:14:50 -07:00 committed by GitHub
parent 2e01f652c1
commit cc6edc39a1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
12 changed files with 10 additions and 9 deletions

View File

@ -28,7 +28,8 @@ might want to derive from this eCommerce data.
--
_Pivoting_ your data involves using at least one field to group it and applying
at least one aggregation. You can preview what the transformed data will look
like, so go ahead and play with it!
like, so go ahead and play with it! You can also enable histogram charts to get
a better understanding of the distribution of values in your data.
For example, you might want to group the data by product ID and calculate the
total number of sales for each product and its average price. Alternatively, you
@ -38,11 +39,11 @@ they purchased. Or you might want to take the currencies or geographies into
consideration. What are the most interesting ways you can transform and
interpret this data?
Go to *Management* > *Elasticsearch* > *Transforms* in {kib} and use the
wizard to create a {transform}:
Go to *Management* > *Stack Management* > *Data* > *Transforms* in {kib} and use
the wizard to create a {transform}:
[role="screenshot"]
image::images/ecommerce-pivot1.jpg["Creating a simple {transform} in {kib}"]
image::images/ecommerce-pivot1.png["Creating a simple {transform} in {kib}"]
In this case, we grouped the data by customer ID and calculated the sum of
products each customer purchased.
@ -59,7 +60,7 @@ We'll accomplish this by using the
on the `order_id` field:
[role="screenshot"]
image::images/ecommerce-pivot2.jpg["Adding multiple aggregations to a {transform} in {kib}"]
image::images/ecommerce-pivot2.png["Adding multiple aggregations to a {transform} in {kib}"]
TIP: If you're interested in a subset of the data, you can optionally include a
<<request-body-search-query,query>> element. In this
@ -220,7 +221,7 @@ can stop it.
You can start, stop, and manage {transforms} in {kib}:
[role="screenshot"]
image::images/manage-transforms.jpg["Managing {transforms} in {kib}"]
image::images/manage-transforms.png["Managing {transforms} in {kib}"]
Alternatively, you can use the
<<start-transform,start {transforms}>> and
@ -249,7 +250,7 @@ data is ingested.
For example, use the *Discover* application in {kib}:
[role="screenshot"]
image::images/ecommerce-results.jpg["Exploring the new index in {kib}"]
image::images/ecommerce-results.png["Exploring the new index in {kib}"]
--
@ -261,4 +262,4 @@ patterns remain.
Now that you've created a simple {transform} for {kib} sample data, consider
possible use cases for your own data. For more ideas, see
<<transform-usage>> and <<transform-examples>>.
<<transform-usage>> and <<transform-examples>>.

Binary file not shown.

Before

Width:  |  Height:  |  Size: 291 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 204 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 355 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 249 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 202 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 183 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 116 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 98 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 138 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 67 KiB

View File

@ -55,7 +55,7 @@ quantity. The result is an entity-centric index that shows the number of sold
items in every product category in the last year.
[role="screenshot"]
image::images/pivot-preview.jpg["Example of a {transform} pivot in {kib}"]
image::images/pivot-preview.png["Example of a {transform} pivot in {kib}"]
IMPORTANT: The {transform} leaves your source index intact. It
creates a new index that is dedicated to the transformed data.