-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updates getting started guide (#41778)
- Loading branch information
Showing
47 changed files
with
612 additions
and
587 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,32 +1,28 @@ | ||
[[add-sample-data]] | ||
== Get up and running with sample data | ||
== Add sample data | ||
|
||
{kib} has several sample data sets that you can use to explore {kib} before loading your own data. | ||
Sample data sets install prepackaged visualizations, dashboards, | ||
{kibana-ref}/canvas-getting-started.html[Canvas workpads], | ||
and {kibana-ref}/maps.html[Maps]. | ||
|
||
The sample data sets showcase a variety of use cases: | ||
These sample data sets showcase a variety of use cases: | ||
|
||
* *eCommerce orders* includes visualizations for product-related information, | ||
such as cost, revenue, and price. | ||
* *Flight data* enables you to view and interact with flight routes. | ||
* *Web logs* lets you analyze website traffic. | ||
* *Flight data* enables you to view and interact with flight routes for four airlines. | ||
|
||
To get started, go to the home page and click the link next to *Add sample data*. | ||
|
||
Once you have loaded a data set, click *View data* to view visualizations in *Dashboard*. | ||
|
||
*Note:* The timestamps in the sample data sets are relative to when they are installed. | ||
If you uninstall and reinstall a data set, the timestamps will change to reflect the most recent installation. | ||
To get started, go to the {kib} home page and click the link underneath *Add sample data*. | ||
|
||
Once you've loaded a data set, click *View data* to view prepackaged | ||
visualizations, dashboards, Canvas workpads, Maps, and Machine Learning jobs. | ||
|
||
[role="screenshot"] | ||
image::images/add-sample-data.png[] | ||
|
||
NOTE: The timestamps in the sample data sets are relative to when they are installed. | ||
If you uninstall and reinstall a data set, the timestamps will change to reflect the most recent installation. | ||
|
||
[float] | ||
==== Next steps | ||
=== Next steps | ||
|
||
Play with the sample flight data in the {kibana-ref}/tutorial-sample-data.html[flight dashboard tutorial]. | ||
* Explore {kib} by following the <<tutorial-sample-data, sample data tutorial>>. | ||
|
||
Learn how to load data, define index patterns and build visualizations by {kibana-ref}/tutorial-build-dashboard.html[building your own dashboard]. | ||
* Learn how to load data, define index patterns, and build visualizations by <<tutorial-build-dashboard, building your own dashboard>>. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,27 +1,57 @@ | ||
[[tutorial-dashboard]] | ||
=== Displaying your visualizations in a dashboard | ||
=== Add visualizations to a dashboard | ||
|
||
A dashboard is a collection of visualizations that you can arrange and share. | ||
You'll build a dashboard that contains the visualizations you saved during | ||
this tutorial. | ||
|
||
. Open *Dashboard*. | ||
. Click *Create new dashboard*. | ||
. Click *Add*. | ||
. On the Dashboard overview page, click *Create new dashboard*. | ||
. Click *Add* in the menu bar. | ||
. Add *Bar Example*, *Map Example*, *Markdown Example*, and *Pie Example*. | ||
|
||
|
||
Your sample dashboard look like this: | ||
|
||
+ | ||
Your sample dashboard should look like this: | ||
+ | ||
[role="screenshot"] | ||
image::images/tutorial-dashboard.png[] | ||
|
||
. Try out the editing controls. | ||
+ | ||
You can rearrange the visualizations by clicking a the header of a | ||
visualization and dragging. The gear icon in the top right of a visualization | ||
displays controls for editing and deleting the visualization. A resize control | ||
is on the lower right. | ||
|
||
To get a link to share or HTML code to embed the dashboard in a web page, save | ||
the dashboard and click *Share*. | ||
. *Save* your dashboard. | ||
|
||
==== Inspect the data | ||
|
||
Seeing visualizations of your data is great, | ||
but sometimes you need to look at the actual data to | ||
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, and then click the icon in the upper right. | ||
. From the *Options* menu, select *Inspect*. | ||
+ | ||
[role="screenshot"] | ||
image::images/tutorial-full-inspect1.png[] | ||
|
||
. To look at the query used to fetch the data for the visualization, select *View > Requests* | ||
in the upper right of the Inspect pane. | ||
|
||
[float] | ||
=== Next steps | ||
|
||
Now that you have a handle on the basics, you're ready to start exploring | ||
your own data with Kibana. | ||
|
||
* See {kibana-ref}/discover.html[Discover] for information about searching and filtering | ||
your data. | ||
* See {kibana-ref}/visualize.html[Visualize] for information about the visualization | ||
types Kibana has to offer. | ||
* See {kibana-ref}/management.html[Management] for information about configuring Kibana | ||
and managing your saved objects. | ||
* See {kibana-ref}/console-kibana.html[Console] to learn about the interactive | ||
console you can use to submit REST requests to Elasticsearch. | ||
|
||
*Save* your dashboard. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,45 +1,53 @@ | ||
[[tutorial-define-index]] | ||
=== Defining your index patterns | ||
=== Define your index patterns | ||
|
||
Index patterns tell Kibana which Elasticsearch indices you want to explore. | ||
An index pattern can match the name of a single index, or include a wildcard | ||
(*) to match multiple indices. | ||
(*) to match multiple indices. | ||
|
||
For example, Logstash typically creates a | ||
series of indices in the format `logstash-YYYY.MMM.DD`. To explore all | ||
of the log data from May 2018, you could specify the index pattern | ||
`logstash-2018.05*`. | ||
|
||
You'll create patterns for the Shakespeare data set, which has an | ||
|
||
[float] | ||
==== Create your first index pattern | ||
|
||
First you'll create index patterns for the Shakespeare data set, which has an | ||
index named `shakespeare,` and the accounts data set, which has an index named | ||
`bank.` These data sets don't contain time-series data. | ||
`bank`. These data sets don't contain time series data. | ||
|
||
. In Kibana, open *Management*, and then click *Index Patterns.* | ||
. If this is your first index pattern, the *Create index pattern* page opens automatically. | ||
Otherwise, click *Create index pattern* in the upper left. | ||
Otherwise, click *Create index pattern*. | ||
. Enter `shakes*` in the *Index pattern* field. | ||
+ | ||
[role="screenshot"] | ||
image::images/tutorial-pattern-1.png[] | ||
|
||
. Click *Next step*. | ||
. In *Configure settings*, click *Create index pattern*. For this pattern, | ||
you don't need to configure any settings. | ||
. Define a second index pattern named `ba*` You don't need to configure any settings for this pattern. | ||
. In *Configure settings*, click *Create index pattern*. | ||
+ | ||
You’re presented a table of all fields and associated data types in the index. | ||
|
||
. Return to the *Index patterns* overview page and define a second index pattern named `ba*`. | ||
|
||
[float] | ||
==== Create an index pattern for time series data | ||
|
||
Now create an index pattern for the Logstash data set. This data set | ||
contains time-series data. | ||
Now create an index pattern for the Logstash index, which | ||
contains time series data. | ||
|
||
. Define an index pattern named `logstash*`. | ||
. Click *Next step*. | ||
. In *Configure settings*, select *@timestamp* in the *Time Filter field name* dropdown menu. | ||
. Open the *Time Filter field name* dropdown and select *@timestamp*. | ||
. Click *Create index pattern*. | ||
|
||
|
||
|
||
|
||
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 | ||
`curl -XGET "http://localhost:9200/_cat/indices"`. | ||
|
||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.