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

[Docs] Update and improve docs for Visualize and Discover #49810

Merged
merged 8 commits into from
Nov 21, 2019

Conversation

wylieconlon
Copy link
Contributor

@wylieconlon wylieconlon commented Oct 30, 2019

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:

  • Removes all documentation that explains elements of the UI without context. This simplifies the documentation significantly.
  • Update screenshots for Discover which have not been updated since 6.0.0
  • Cross-links to the index pattern documentation in the first reference per page because users have been confused about the concept of an "index pattern"
  • Remove redundant wording on some aggregations such as the Min/max/average/sum aggregations
  • Groups maps and time-series visualizations better, specifically trying to highlight how Timelion is no longer shown by default, and how Coordinate Maps and Region Maps are visible in OSS by default but not in x-pack
  • Merges markdown and controls into one page and added "For use in dashboard" context
  • Explains how to use the Include/Exclude options on terms, in particular clarifying Exclude filter in aggregations only supports syntax for strings #12421

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

@wylieconlon wylieconlon added Team:Docs Team:Visualizations Visualization editors, elastic-charts and infrastructure release_note:skip Skip the PR/issue when compiling release notes v7.5.0 labels Oct 30, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-docs (Team:Docs)

@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@wylieconlon wylieconlon marked this pull request as ready for review October 31, 2019 18:07
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Contributor

@gchaps gchaps left a 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?

docs/discover/field-filter.asciidoc Outdated Show resolved Hide resolved
docs/discover/field-filter.asciidoc Outdated Show resolved Hide resolved
Copy link
Contributor

@KOTungseth KOTungseth left a 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.

docs/user/visualize.asciidoc Outdated Show resolved Hide resolved
@@ -0,0 +1,101 @@
[[supported-aggregations]]
=== Supported aggregations
Copy link
Contributor

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?

Copy link
Contributor Author

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

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
Copy link
Contributor

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.

All of these visualizations support:

**Metric Aggregations:**

Copy link
Contributor

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:**

Copy link
Contributor

Choose a reason for hiding this comment

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

What are bucket aggregations?

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 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

Copy link
Contributor

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?

Copy link
Contributor Author

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/metric.asciidoc Show resolved Hide resolved
docs/visualize/most-frequent.asciidoc Outdated Show resolved Hide resolved
docs/visualize/most-frequent.asciidoc Outdated Show resolved Hide resolved
docs/visualize/aggregations.asciidoc Outdated Show resolved Hide resolved
* 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
Copy link
Contributor

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.

<<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.
Copy link
Contributor Author

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.

@wylieconlon
Copy link
Contributor Author

@KOTungseth @gchaps Any concerns with merging this? I think I've addressed your feedback so far.

Copy link
Contributor

@gchaps gchaps left a comment

Choose a reason for hiding this comment

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

Discover LGTM.

KOTungseth pushed a commit to KOTungseth/kibana that referenced this pull request Nov 21, 2019
)

* [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
KOTungseth pushed a commit to KOTungseth/kibana that referenced this pull request Nov 21, 2019
)

* [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
KOTungseth added a commit that referenced this pull request Nov 22, 2019
…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
KOTungseth added a commit that referenced this pull request Nov 22, 2019
…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
@wylieconlon wylieconlon deleted the docs-kibana-app branch December 9, 2019 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:skip Skip the PR/issue when compiling release notes Team:Docs Team:Visualizations Visualization editors, elastic-charts and infrastructure v7.5.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Exclude Pattern/Include pattern in docs don't show they are available only on significant terms
4 participants