-
Notifications
You must be signed in to change notification settings - Fork 73
IngestArch: Add introductory content #19
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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,4 +1,3 @@ | ||
[discrete] | ||
[[use-case-arch]] | ||
== Ingest architectures and use cases | ||
|
||
|
This file contains hidden or 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 hidden or 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,5 +1,49 @@ | ||
[[intro-ingest-architectures]] | ||
== Overview | ||
|
||
include::arch-list.asciidoc[] | ||
You can ingest data into {es} using {agent}, {beats}, {ls}, Elastic language clients, Workplace Search content connectors, or the Enterprise Search web crawler. | ||
|
||
Which option is best? Generally speaking, your best choice is the _simplest option that meets your needs_ and satisfies your use case. | ||
|
||
We can help you determine exactly what that option is. | ||
|
||
TIP: {agent} writing directly to {es} on {ecloud} provides the easiest and fastest time to value for most users. {ess-leadin-short} | ||
|
||
[discrete] | ||
[[agent]] | ||
=== {agent} and agent integrations | ||
Start by checking out {agent} and agent https://www.elastic.co/integrations/[{agent} integrations]. | ||
|
||
Integrations offer advantages beyond easier data collection--advantages such as dashboards, central agent management, and easy enablement of https://www.elastic.co/products/[Elastic solutions] for Security, Observability, and Enterprise Search. | ||
|
||
Integrations are available for many popular services and platforms, as well as generic input types such as custom log files and APIs. | ||
And the list continue to grow. | ||
|
||
TIP: If you don't find an integration for your data source, try {beats-ref}/beats-reference.html[Beats] or Beats modules. | ||
If you don't find a Beat or a Beats module for your data source, check out {logstash-ref}/input-plugins.html[Logstash inputs]. | ||
|
||
If your data requires additional processing, we can help with that, too. | ||
|
||
[discrete] | ||
[[processing]] | ||
=== Additional processing | ||
|
||
Do you need to: | ||
|
||
* *Sanitize* or *enrich raw data* at the source? | ||
+ | ||
{agent} integrations offer agent processors to handle this work. | ||
({beats} offer {beats-ref}/filtering-and-enhancing-data.html[{beats} processors.]) | ||
|
||
* Convert data to *{ecs-ref}[Elastic Common Schema (ECS)]*, *normalize* field data, or *enrich incoming data*? | ||
+ | ||
Try an ingest pipeline for {ref}/ingest.html#pipelines-for-fleet-elastic-agent[{agent}] or {ref}/ingest.html#pipelines-for-beats[{beats}]. | ||
|
||
* *Define or alter schema at query time*? | ||
+ | ||
Try {ref}/runtime.html[runtime fields]. | ||
|
||
* *Enrich data*? Or do *something else*? | ||
+ | ||
Check out {ref}/filter-plugins.html[{ls} filter plugins]. | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 content lives on in the latest Ingest overview #1373