Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion docs/en/ingest-arch/arch-list.asciidoc
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@
[discrete]
[[use-case-arch]]
== Ingest architectures and use cases

Expand Down
2 changes: 2 additions & 0 deletions docs/en/ingest-arch/index.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ include::{docs-root}/shared/attributes.asciidoc[]

include::intro.asciidoc[]

include::arch-list.asciidoc[]

include::1a-agent.asciidoc[]

include::1b-apis.asciidoc[]
Expand Down
46 changes: 45 additions & 1 deletion docs/en/ingest-arch/intro.asciidoc
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.
Copy link
Contributor Author

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


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