iSharkFly-Docs
/
opensearch-docs-cn
mirror of https://github.com/iSharkFly-Docs/opensearch-docs-cn
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Alphabetize by title (#6608) 

* Alphabetize by title

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>

* Alphabetize by title

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>

---------

Signed-off-by: Melissa Vagi <vagimeli@amazon.com>
This commit is contained in:
Melissa Vagi 2024-03-06 12:19:41 -07:00 committed by GitHub
parent c08cd98952
commit a742d47b01
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
9 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_data-prepper/common-use-cases/anomaly-detection.md
View File

@ -2,7 +2,7 @@
layout: default layout: default
title: Anomaly detection title: Anomaly detection
parent: Common use cases parent: Common use cases
nav_order: 30 nav_order: 5
--- ---
# Anomaly detection # Anomaly detection

2
_data-prepper/common-use-cases/codec-processor-combinations.md
View File

@ -2,7 +2,7 @@
layout: default layout: default
title: Codec processor combinations title: Codec processor combinations
parent: Common use cases parent: Common use cases
nav_order: 25 nav_order: 10
--- ---
# Codec processor combinations # Codec processor combinations

2
_data-prepper/common-use-cases/event-aggregation.md
View File

@ -2,7 +2,7 @@
layout: default layout: default
title: Event aggregation title: Event aggregation
parent: Common use cases parent: Common use cases
nav_order: 40 nav_order: 25
--- ---
# Event aggregation # Event aggregation

2
_data-prepper/common-use-cases/log-analytics.md
View File

@ -2,7 +2,7 @@
layout: default layout: default
title: Log analytics title: Log analytics
parent: Common use cases parent: Common use cases
nav_order: 10 nav_order: 30
--- ---
# Log analytics # Log analytics

2
_data-prepper/common-use-cases/log-enrichment.md
View File

@ -2,7 +2,7 @@
layout: default layout: default
title: Log enrichment title: Log enrichment
parent: Common use cases parent: Common use cases
nav_order: 50 nav_order: 35
--- ---
# Log enrichment # Log enrichment

2
_data-prepper/common-use-cases/metrics-traces.md
View File

@ -2,7 +2,7 @@
layout: default layout: default
title: Deriving metrics from traces title: Deriving metrics from traces
parent: Common use cases parent: Common use cases
nav_order: 60 nav_order: 20
--- ---
# Deriving metrics from traces # Deriving metrics from traces

2
_data-prepper/common-use-cases/s3-logs.md
View File

@ -2,7 +2,7 @@
layout: default layout: default
title: S3 logs title: S3 logs
parent: Common use cases parent: Common use cases
nav_order: 20 nav_order: 40
--- ---
# S3 logs # S3 logs

2
_data-prepper/common-use-cases/text-processing.md
View File

@ -2,7 +2,7 @@
layout: default layout: default
title: Text processing title: Text processing
parent: Common use cases parent: Common use cases
nav_order: 35 nav_order: 55
--- ---
# Text processing # Text processing

4
_data-prepper/common-use-cases/trace-analytics.md
View File

@ -2,7 +2,7 @@
layout: default layout: default
title: Trace analytics title: Trace analytics
parent: Common use cases parent: Common use cases
nav_order: 5 nav_order: 60
--- ---
# Trace analytics # Trace analytics
@ -15,7 +15,7 @@ When using Data Prepper as a server-side component to collect trace data, you ca
The following flowchart illustrates the trace analytics workflow, from running OpenTelemetry Collector to using OpenSearch Dashboards for visualization. The following flowchart illustrates the trace analytics workflow, from running OpenTelemetry Collector to using OpenSearch Dashboards for visualization.
<img src="{{site.url}}{{site.baseurl}}/images/data-prepper/trace-analytics/trace-analytics-components.jpg" alt="Trace analyticis component overview">{: .img-fluid} <img src="{{site.url}}{{site.baseurl}}/images/data-prepper/trace-analytics/trace-analytics-components.jpg" alt="Trace analytics component overview">{: .img-fluid}
To monitor trace analytics, you need to set up the following components in your service environment: To monitor trace analytics, you need to set up the following components in your service environment:
- Add **instrumentation** to your application so it can generate telemetry data and send it to an OpenTelemetry collector. - Add **instrumentation** to your application so it can generate telemetry data and send it to an OpenTelemetry collector.