-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Updates getting started guide #41778
Conversation
Pinging @elastic/kibana-docs |
docs/getting-started.asciidoc
Outdated
|
||
include::getting-started/tutorial-sample-remove.asciidoc[] | ||
* Learn how to load data, define index patterns, and build visualizations by {kibana-ref}/tutorial-build-dashboard.html[building your own dashboard]. |
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.
Avg Ticket Price
is cut off in this image. Is that intended?
. In the *Buckets* pane, select *Add > Split group*. | ||
. In the *Aggregation* dropdown, select *Terms*. | ||
. In the *Field* dropdown, select *Carrier*. | ||
. Set *Descending* to 4. |
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.
Should 4 be 4
?
understand what's really going on. You can inspect the data behind any visualization | ||
and view the {es} query used to retrieve it. | ||
|
||
. In the dashboard, hover the pointer over the pie chart. |
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.
Why?
|
||
Now that you have a handle on the {kib} basics, you might be interested in: | ||
|
||
* <<tutorial-build-dashboard, Building your own dashboard>>. You’ll learn how to load your own |
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.
For consistency, how about:
- Building your own dashboard.
- Discovering your data.
- Visualizing your data.
- Sharing your dashboard.
@@ -1,12 +1,15 @@ | |||
[[tutorial-build-dashboard]] | |||
== Building your own dashboard | |||
== Build your own dashboard |
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 page is short. Maybe combine Build your own dashboard
and Load sample data
?
. Return to the *Index patterns* overview page and define a second index pattern named `ba*`. | ||
|
||
[float] | ||
==== Create an index pattern for time-series data |
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.
time-series
should be time series
|
||
Now create an index pattern for the Logstash data set. This data set | ||
Now create an index pattern for the Logstash index, which | ||
contains time-series data. |
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.
time-series
should be time series
. Click *Create index pattern*. | ||
|
||
[float] | ||
==== A note about index patterns |
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.
Does this have to be its own section? Or could it be:
NOTE: When you define an index pattern, the indices that match that pattern must exist in Elasticsearch and they must contain data. To check which indices are available, go to Dev Tools > Console and enter GET _cat/indices
. Alternately, use available, go to Dev Tools > Console and enter GET _cat/indices
. Alternately, use curl -XGET "http://localhost:9200/_cat/indices"
. curl -XGET "http://localhost:9200/_cat/indices"
.
|
||
. To look at the query used to fetch the data for the visualization, select *View > Requests* | ||
in the upper right of the Inspect pane. | ||
|
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.
Could we move the dashboard image from Build your own dashboard
to here?
in the upper right of the Inspect pane. | ||
|
||
[float] | ||
=== Wrapping up |
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.
We sometimes call these sections Next steps
, and we sometimes call them Wrapping up
. Should we choose one for consistency?
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.
LGTM
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.
Perfecto!
Summary
This PR:
[skip ci]