-
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
[Docs] Update and improve docs for Visualize and Discover #49810
Conversation
Pinging @elastic/kibana-docs (Team:Docs) |
Pinging @elastic/kibana-app (Team:KibanaApp) |
💚 Build Succeeded |
💚 Build Succeeded |
💚 Build Succeeded |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed the Discover section. Kaarina is reviewing Visualize.
There are also some old screenshots in document.context.asciidoc. Would you mind updating those screenshots as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a great PR! Thank you so much for making these changes. I'm about half way through on my own changes. I will pick this up again very soon.
@@ -0,0 +1,101 @@ | |||
[[supported-aggregations]] | |||
=== Supported aggregations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to clarify, placing Supported aggregations
here means that TSVB, Timelion, Coordinate Maps, Region Maps, Markdown and Dashboard controls, and Vega do not use these aggregations.
Is that right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is correct. Coordinate maps and region maps actually do use a subset of these, but those visualizations are now hidden by default in the basic license in 7.5
docs/visualize/aggregations.asciidoc
Outdated
aggregation. | ||
* Top Hit: Uses the {ref}/search-aggregations-metrics-top-hits-aggregation.html[_top hits_] | ||
aggregation to return a sample of individual documents. If more than one document is matched by this aggregation, you must choose a technique for combining the values. These techniques are average, min, max, and sum. | ||
* Percentiles: The {ref}/search-aggregations-metrics-percentile-aggregation.html[_percentile_] aggregation divides the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would use the same formatting as the previous bullet.
docs/visualize/aggregations.asciidoc
Outdated
All of these visualizations support: | ||
|
||
**Metric Aggregations:** | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are metric aggregations?
*Max Bucket*:: The {ref}/search-aggregations-pipeline-avg-bucket-aggregation.html[_max bucket_]calculates the maximum value of a specified metric in a sibling aggregation | ||
|
||
**Bucket Aggregations:** | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are bucket aggregations?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't want to redefine every term here, but this is an Elasticsearch term that we use throughout the Visualize apps https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that we shouldn't double-document the definition, but does bucket aggregation mean the same thing in Elasticsearch as it does in Kibana?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They have the same meaning and we use the same words in both places (with few exceptions such as Unique Count)
docs/visualize/aggregations.asciidoc
Outdated
* Top Hit: Uses the {ref}/search-aggregations-metrics-top-hits-aggregation.html[_top hits_] | ||
aggregation to return a sample of individual documents. If more than one document is matched by this aggregation, you must choose a technique for combining the values. These techniques are average, min, max, and sum. | ||
* Percentiles: The {ref}/search-aggregations-metrics-percentile-aggregation.html[_percentile_] aggregation divides the | ||
values in a numeric field into percentile bands that you specify. Select a field from the drop-down, then specify one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it necessary to keep the task content in these definitions? I think we can remove Select a field from the drop-down, then specify one or more ranges in the *Percentiles* fields. Click the *X* to remove a percentile field. Click *+ Add* to add a percentile field.
and relocate it at point of use.
docs/user/visualize.asciidoc
Outdated
<<goal-chart,Goal and Gauge>>:: Display a gauge. | ||
<<TSVB,TSVB>>:: Visualize time series data using pipeline aggregations. | ||
<<timelion,_Timelion_>>:: Compute and combine data from multiple time series | ||
data sets. Hidden by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to update Timelion. It's shown by default.
@KOTungseth @gchaps Any concerns with merging this? I think I've addressed your feedback so far. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discover LGTM.
…51359) * [Docs] Update and improve docs for Visualize and Discover * Create a new section for default editor docs * Fix significant terms link * Writer changes * Remove pages that aren't helpful to users * More writer changes
…51360) * [Docs] Update and improve docs for Visualize and Discover * Create a new section for default editor docs * Fix significant terms link * Writer changes * Remove pages that aren't helpful to users * More writer changes
The biggest change here is to create a new grouping of "Most frequently used visualizations" which share the same logic for being able to create aggregations. We call this the default editor, and because it's shared it makes sense to document the editor in one way and only document exceptions to the rule as needed.
The other changes made in this PR:
Updated pages:
http://kibana_49810.docs-preview.app.elstc.co/guide/en/kibana/master/field-filter.html
http://kibana_49810.docs-preview.app.elstc.co/guide/en/kibana/master/visualize.html
[skip ci]
Closes #12573