-
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] Updates add data content #81093
Changes from 1 commit
2938e3e
b862531
0457d09
7f06994
ad122d0
3717987
0be0960
1d6e585
b9e7e54
572a496
e845479
ec19d62
a3a1481
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,74 +1,65 @@ | ||
[[connect-to-elasticsearch]] | ||
== Add data to {kib} | ||
++++ | ||
<titleabbrev>Add data</titleabbrev> | ||
++++ | ||
|
||
The fastet way to add data to {kib} is to use one of the built-in options, | ||
available from the home page. You can: | ||
|
||
* Add data from popular apps and services | ||
* Add data using an Elastic Agent | ||
* Upload a file | ||
The fastest way to add data to {kib} is to use one of the built-in options, | ||
available from the home page. You can collect data from an app or service | ||
or upload a file that contains your data. If you're not ready to use your own data, | ||
add a <<get-started, sample data set>> and give {kib} a test drive. | ||
|
||
[role="screenshot"] | ||
image::images/add-data-home.png[Built-in options for adding data to Kibana] | ||
|
||
If you're not ready to use your own data, you can add a <<get-started, sample data set>> | ||
to give {kib} a test drive. | ||
|
||
[float] | ||
[[add-data-tutorial-kibana]] | ||
=== Add data tutorials | ||
=== Add data | ||
|
||
These tutorials guide you through installing and configuring a | ||
Beats data shipper to collect metrics, logs, security events, and application data and send it to {es}. | ||
You can then use the pre-built dashboards to explore and analyze the data. | ||
The *Add data* tutorials help you quickly get up and running with metrics data, | ||
log analytics, security events, and application data. These tutorials walk you | ||
through installing and configuring a Beats data shipper to periodically collect | ||
and send data to {es}. You can then use the pre-built dashboards to explore and analyze the data. | ||
|
||
If a tutorial doesn’t exist for your data, go to the {beats-ref}/beats-reference.html[Beats overview] | ||
to learn about other data shippers in the Beats family. | ||
|
||
[role="screenshot"] | ||
image::images/add-data-tutorials.png[Add Data tutorials] | ||
|
||
|
||
[discrete] | ||
[[add-data-fleet-kibana]] | ||
=== Add an Elatic Agent | ||
=== Add Elastic Agent | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the split between add data and add Elastic agent is fine now, because we have them in product. We'll have to work with @mostlyjason on when we can begin to default to agent and remove add data from the docs (similarly to how we did with Lens) and eventually, product There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These two things are very similar, integrations with Agent + Fleet are the next generation of modules. I wonder if we can spin this in a way with "get a sneak peak of where we're going with.." or something along those lines. |
||
|
||
beta[] | ||
beta[] *Elastic Agent* is alternative to installing and managing Beats individually. | ||
Using the *Fleet* UI, you can add | ||
and manage integrations for popular services and platforms, giving you | ||
an easy way to collect data. The integrations also | ||
ship with out-of-the-box assets, including dashboards visualizations. | ||
|
||
Fleet is a single, unified way to collect logs and metrics from systems | ||
and services across your organization. You don't have to install multiple | ||
Beats and other agents, making easier to deploy policies across your infrastructure. | ||
For more information, see | ||
To get started, refer to | ||
{ingest-guide}/ingest-management-getting-started.html[Quick start: Get logs and metrics into the Elastic Stack]. | ||
|
||
[role="screenshot"] | ||
image::images/add-data-fleet.png[Add data using Fleet] | ||
|
||
[float] | ||
[discrete] | ||
[[upload-data-kibana]] | ||
=== Upload a file | ||
|
||
experimental[] | ||
|
||
To visualize data in a CSV, JSON, or log file, you can upload it using the File | ||
Data Visualizer. On the home page, click *Upload a file*, and | ||
then drag your file into the *File Data Visualizer*. | ||
You can upload a file up to 100 MB. This value is configurable up to 1 GB in | ||
experimental[] If your data is in a CSV, JSON, or log file, you can upload it using the File | ||
Data Visualizer. You can upload a file up to 100 MB. This value is configurable up to 1 GB in | ||
<<kibana-ml-settings, Advanced Settings>>. | ||
|
||
[role="screenshot"] | ||
image::images/add-data-fv.png[File Data Visualizer] | ||
|
||
The File Data Visualizer uses the {ref}/ml-find-file-structure.html[find_file_structure API] to analyze | ||
the uploaded file and to suggest ingest pipelines and mappings for your data. | ||
|
||
NOTE: This feature is not intended for use as part of a | ||
repeated production process, but rather for the initial exploration of your data. | ||
|
||
To visualize geospatial data in a point or shape file, use the <<import-geospatial-data, GeoJSON Upload>> | ||
feature in *Maps*. | ||
|
||
[discrete] | ||
=== Or, load your data yourself | ||
=== Load data on your own | ||
|
||
You can also index your data into Elasticsearch with REST APIs or client libraries. | ||
After you add your data, you'll need to create an <<index-patterns,index pattern>>. | ||
You can index your data into Elasticsearch with {ref}/getting-started-index.html[REST APIs] | ||
or https://www.elastic.co/guide/en/elasticsearch/client/index.html[client libraries]. | ||
After you add your data, you must create an <<index-patterns,index pattern>> to tell | ||
{kib} where to find the 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.
Similar to the comment from Nathan, should we simply have "Add data" here to avoid confusion?