mirror of
https://github.com/iSharkFly-Docs/opensearch-docs-cn
synced 2025-02-10 11:04:42 +00:00
7ac74ec7a6
* for new page how to analyze Jaeger trace data Signed-off-by: alicejw <alicejw@amazon.com> * remove old image Signed-off-by: alicejw <alicejw@amazon.com> * for new information and doc writer checklist Signed-off-by: alicejw <alicejw@amazon.com> * for new information and doc writer checklist Signed-off-by: alicejw <alicejw@amazon.com> * small rewrite Signed-off-by: alicejw <alicejw@amazon.com> * new clean images from Dashboards URL directly Signed-off-by: alicejw <alicejw@amazon.com> * for additional information Signed-off-by: alicejw <alicejw@amazon.com> * remove blank lines Signed-off-by: alicejw <alicejw@amazon.com> * for tech review feedback updates Signed-off-by: alicejw <alicejw@amazon.com> * add requirements section Signed-off-by: alicejw <alicejw@amazon.com> * for new procedure Signed-off-by: alicejw <alicejw@amazon.com> * for tech review feedback updates Signed-off-by: alicejw <alicejw@amazon.com> * continued updates Signed-off-by: alicejw <alicejw@amazon.com> * for docker compose file instructions Signed-off-by: alicejw <alicejw@amazon.com> * for docker usage instruction Signed-off-by: alicejw <alicejw@amazon.com> * for step 2 view dashboards Signed-off-by: alicejw <alicejw@amazon.com> * for additional link provided in tech review Signed-off-by: alicejw <alicejw@amazon.com> * for link to index page to introduce the feature Signed-off-by: alicejw <alicejw@amazon.com> * final checklist Signed-off-by: alicejw <alicejw@amazon.com> * add warning not to use sample file in prod env Signed-off-by: alicejw <alicejw@amazon.com> * updated docker file that is safe for prod env, remove warning note for previous file Signed-off-by: alicejw <alicejw@amazon.com> * for small update to parent page Signed-off-by: alicejw <alicejw@amazon.com> * for tech review Signed-off-by: alicejw <alicejw@amazon.com> * typo fix for font Signed-off-by: alicejw <alicejw@amazon.com> * for doc review #1 feedback updates Signed-off-by: alicejw <alicejw@amazon.com> * for doc review feedback #2 updates Signed-off-by: alicejw <alicejw@amazon.com> * for a couple minor changes Signed-off-by: alicejw <alicejw@amazon.com> * spell out dashboard URI directly to trace analytics for accessibility. With URL obfuscated, this would not get spelled out in the vision-impaired app that scans through.it would simply read the title only Signed-off-by: alicejw <alicejw@amazon.com> * need to add additional step from eng to generate sample data Signed-off-by: alicejw <alicejw@amazon.com> * for additional step image of sample app Signed-off-by: alicejw <alicejw@amazon.com> * rename step numbers Signed-off-by: alicejw <alicejw@amazon.com> * minor fix heading levels Signed-off-by: alicejw <alicejw@amazon.com> * updates recommended by the editorial reviewer Signed-off-by: alicejw <alicejw@amazon.com> * clarify Spans window function Signed-off-by: alicejw <alicejw@amazon.com> * clarified individual trace details section Signed-off-by: alicejw <alicejw@amazon.com> Signed-off-by: alicejw <alicejw@amazon.com>
24 lines
1.2 KiB
Markdown
24 lines
1.2 KiB
Markdown
---
|
|
layout: default
|
|
title: Trace analytics
|
|
nav_order: 60
|
|
has_children: true
|
|
has_toc: false
|
|
---
|
|
|
|
# Trace analytics
|
|
|
|
Trace analytics provides a way to ingest and visualize [OpenTelemetry](https://opentelemetry.io/) data in OpenSearch. This data can help you find and fix performance problems in distributed applications.
|
|
|
|
A single operation, such as a user choosing a button, can trigger an extended series of events. The frontend might call a backend service, which calls another service, which queries a database, processes the data, and sends it to the original service, which sends a confirmation to the frontend.
|
|
|
|
Trace analytics can help you visualize this flow of events and identify performance problems, as shown in the following image.
|
|
|
|
|
|
|
|
## Trace analytics with Jaeger data
|
|
|
|
The trace analytics functionality in the OpenSearch Observability plugin supports Jaeger trace data. If you use OpenSearch as the backend for Jaeger trace data, you can use the built-in trace analytics capabilities.
|
|
|
|
To set up your environment to perform trace analytics, see [Analyze Jaeger trace data]({{site.url}}{{site.baseurl}}/observability-plugin/trace/trace-analytics-jaeger/).
|