Skip to content

Commit 397d5cd

Browse files
lcawllcawl
committed
Change section order
1 parent fd3cdeb commit 397d5cd

File tree

1 file changed

+63
-63
lines changed

1 file changed

+63
-63
lines changed

‎get-started/the-stack.md‎

Lines changed: 63 additions & 63 deletions
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,15 @@ applies_to:
1313
---
1414
# {{stack}} and the {{search-platform}}
1515

16-
The [{{search-platform}}](https://www.elastic.co/platform) is the full suite of products and features available in [{{ecloud}}](https://www.elastic.co/cloud) including orchestration, autoscaling, and cloud-native features.
16+
The [{{search-platform}}](https://www.elastic.co/platform) is the full suite of products and features available in {{ecloud}} including its unique orchestration, autoscaling, and cloud-native features.
1717

18-
The following products are the open source foundation of the {{search-platform}}:
18+
The open source foundation of the {{search-platform}} consists of:
1919

2020
- [{{es}}](#stack-components-elasticsearch): The distributed data store and search engine that handles indexing, querying, and analytics.
2121
- [{{kib}}](#stack-components-kibana): The user interface with dashboards, visualizations, and management tools.
2222

23-
All [deployment options](/get-started/deployment-options.md) (such as {{ecloud}} and self-managed clusters) include {{es}}.
24-
{{kib}} is not required to use {{es}}, but is included by default when you use deployment methods such as {{serverless-full}}.
23+
All deployment options (such as {{ecloud}} or self-managed clusters) include {{es}}.
24+
{{kib}} is not required to use {{es}}, but is included by default in {{serverless-full}}.
2525

2626
Depending on your use case, you might need to install more products that work together with {{es}} and {{kib}} (referred to as the [{{stack}}](https://www.elastic.co/elastic-stack) or ELK). For example:
2727

@@ -35,65 +35,6 @@ The {{stack}} includes products for ingesting, storing, and exploring data at sc
3535

3636
Continue reading to learn how these products work together.
3737

38-
## Ingest [_ingest]
39-
40-
There are multiple methods for ingesting data.
41-
The best approach depends on the kind of data you're ingesting and your specific use case.
42-
For example, you can collect and ship logs, metrics, and other types of data with {{agent}} or collect detailed performance information with {{product.apm}}.
43-
If you want to transform and enrich data before it's stored, you can use {{es}} ingest pipelines or {{ls}}.
44-
45-
Trying to decide which ingest components to use? Refer to [](/manage-data/ingest.md) and [](/manage-data/ingest/tools.md).
46-
47-
### {{agent}} and {{integrations}}[stack-components-agent]
48-
49-
{{agent}} is a single, unified way to add monitoring for logs, metrics, and other types of data to a host.
50-
It can also protect hosts from security threats, query data from operating systems, and forward data from remote services or hardware.
51-
Each agent has a single policy to which you can add [integrations](integration-docs://reference/index.md) for new data sources, security protections, and more.
52-
You can also use [{{agent}} processors](/reference/fleet/agent-processors.md) to sanitize or enrich your data.
53-
54-
{{fleet}} enables you to centrally manage {{agents}} and their policies.
55-
Use {{fleet}} to monitor the state of all your {{agents}}, manage agent policies, and upgrade {{agent}} binaries or integrations.
56-
57-
[Learn more about {{agent}}](/reference/fleet/index.md).
58-
59-
### {{product.apm}} [stack-components-apm]
60-
61-
{{product.apm}} is an application performance monitoring system.
62-
It allows you to monitor software services and applications in real-time by collecting detailed performance information on response time for incoming requests, database queries, calls to caches, external HTTP requests, and more.
63-
This makes it easy to pinpoint and fix performance problems quickly.
64-
65-
[Learn more about {{product.apm}}](/solutions/observability/apm/index.md).
66-
67-
### OpenTelemetry Collector [stack-components-otel]
68-
69-
[OpenTelemetry](https://opentelemetry.io/docs)(OTel) is a vendor-neutral observability framework for collecting, processing, and exporting telemetry data. Elastic is a member of the Cloud Native Computing Foundation (CNCF) and active contributor to the OpenTelemetry project.
70-
71-
In addition to supporting upstream OTel development, Elastic provides Elastic Distributions of OpenTelemetry (EDOT), specifically designed to work with {{product.observability}}.
72-
73-
[Learn more about EDOT](opentelemetry://reference/index.md).
74-
75-
### {{beats}} [stack-components-beats]
76-
77-
:::{include} /manage-data/_snippets/beats.md
78-
:::
79-
80-
[Learn more about {{beats}}](beats://reference/index.md).
81-
82-
### {{es}} ingest pipelines [stack-components-ingest-pipelines]
83-
84-
Ingest pipelines let you perform common transformations on your data before indexing them into {{es}}.
85-
You can configure one or more "processor" tasks to run sequentially, making specific changes to your documents before storing them in {{es}}.
86-
87-
[Learn more about ingest pipelines](/manage-data/ingest/transform-enrich/ingest-pipelines.md).
88-
89-
### {{ls}} [stack-components-logstash]
90-
91-
{{ls}} is a data collection engine with real-time pipelining capabilities.
92-
It can dynamically unify data from disparate sources and normalize the data into destinations of your choice.
93-
{{ls}} supports a broad array of input, filter, and output plugins, with many native codecs further simplifying the ingestion process.
94-
95-
[Learn more about {{ls}}](logstash://reference/index.md).
96-
9738
## Store, search, and analyze [_store]
9839

9940
{{es}} is the distributed storage, search, and analytics engine.
@@ -151,3 +92,62 @@ Each solution or project type provides access to customized features in {{kib}}
15192
For secure, automated access, you can create and manage API keys to authenticate your scripts and applications.
15293

15394
[Learn more about {{kib}}](/explore-analyze/index.md).
95+
96+
## Ingest [_ingest]
97+
98+
There are multiple methods for ingesting data.
99+
The best approach depends on the kind of data you're ingesting and your specific use case.
100+
For example, you can collect and ship logs, metrics, and other types of data with {{agent}} or collect detailed performance information with {{product.apm}}.
101+
If you want to transform and enrich data before it's stored, you can use {{es}} ingest pipelines or {{ls}}.
102+
103+
Trying to decide which ingest components to use? Refer to [](/manage-data/ingest.md) and [](/manage-data/ingest/tools.md).
104+
105+
### {{agent}} and {{integrations}}[stack-components-agent]
106+
107+
{{agent}} is a single, unified way to add monitoring for logs, metrics, and other types of data to a host.
108+
It can also protect hosts from security threats, query data from operating systems, and forward data from remote services or hardware.
109+
Each agent has a single policy to which you can add [integrations](integration-docs://reference/index.md) for new data sources, security protections, and more.
110+
You can also use [{{agent}} processors](/reference/fleet/agent-processors.md) to sanitize or enrich your data.
111+
112+
{{fleet}} enables you to centrally manage {{agents}} and their policies.
113+
Use {{fleet}} to monitor the state of all your {{agents}}, manage agent policies, and upgrade {{agent}} binaries or integrations.
114+
115+
[Learn more about {{agent}}](/reference/fleet/index.md).
116+
117+
### {{product.apm}} [stack-components-apm]
118+
119+
{{product.apm}} is an application performance monitoring system.
120+
It allows you to monitor software services and applications in real-time by collecting detailed performance information on response time for incoming requests, database queries, calls to caches, external HTTP requests, and more.
121+
This makes it easy to pinpoint and fix performance problems quickly.
122+
123+
[Learn more about {{product.apm}}](/solutions/observability/apm/index.md).
124+
125+
### OpenTelemetry Collector [stack-components-otel]
126+
127+
[OpenTelemetry](https://opentelemetry.io/docs)(OTel) is a vendor-neutral observability framework for collecting, processing, and exporting telemetry data. Elastic is a member of the Cloud Native Computing Foundation (CNCF) and active contributor to the OpenTelemetry project.
128+
129+
In addition to supporting upstream OTel development, Elastic provides Elastic Distributions of OpenTelemetry (EDOT), specifically designed to work with {{product.observability}}.
130+
131+
[Learn more about EDOT](opentelemetry://reference/index.md).
132+
133+
### {{beats}} [stack-components-beats]
134+
135+
:::{include} /manage-data/_snippets/beats.md
136+
:::
137+
138+
[Learn more about {{beats}}](beats://reference/index.md).
139+
140+
### {{es}} ingest pipelines [stack-components-ingest-pipelines]
141+
142+
Ingest pipelines let you perform common transformations on your data before indexing them into {{es}}.
143+
You can configure one or more "processor" tasks to run sequentially, making specific changes to your documents before storing them in {{es}}.
144+
145+
[Learn more about ingest pipelines](/manage-data/ingest/transform-enrich/ingest-pipelines.md).
146+
147+
### {{ls}} [stack-components-logstash]
148+
149+
{{ls}} is a data collection engine with real-time pipelining capabilities.
150+
It can dynamically unify data from disparate sources and normalize the data into destinations of your choice.
151+
{{ls}} supports a broad array of input, filter, and output plugins, with many native codecs further simplifying the ingestion process.
152+
153+
[Learn more about {{ls}}](logstash://reference/index.md).

0 commit comments

Comments
 (0)