Adds Jaeger trace data for analytics documentation#2374
Adds Jaeger trace data for analytics documentation#2374alicejw1 merged 35 commits intoopensearch-project:mainfrom
Conversation
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
would suggest updating the first section to:The Trace analytics functionality in OpenSearch Observability plugin now supports Jaeger trace data. Users that use OpenSearch as the backend for their Jaeger trace data can now benefit from the analysis capabilities built into OpenSearch Trace analytics. This adds to the existing support for OTEL formatted trace data. When you use trace analytics, you can now select from two data sources: If you currently store your Jaeger trace data in OpenSearch, you can now use the capabilities built into Trace analytics to analyze the error rates and latencies. You can also filter the traces and look into the span details of a trace to pinpoint any service issues. |
|
would suggest updating the first section to: The Trace analytics functionality in OpenSearch Observability plugin now supports Jaeger trace data. Users that use OpenSearch as the backend for their Jaeger trace data can now benefit from the analysis capabilities built into OpenSearch Trace analytics. This adds to the existing support for OTEL formatted trace data. When you use trace analytics, you can now select from two data sources: If you currently store your Jaeger trace data in OpenSearch, you can now use the capabilities built into Trace analytics to analyze the error rates and latencies. You can also filter the traces and look into the span details of a trace to pinpoint any service issues. |
Signed-off-by: alicejw <alicejw@amazon.com>
|
Tech review comments are now incorporated. (except need one more command from @derek-ho ) Thanks |
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
|
Updated PDFs after final clarification meeting and small updates. |
vagimeli
left a comment
There was a problem hiding this comment.
@alicejw-aws Made some comments and suggestions. Good work!
hdhalter
left a comment
There was a problem hiding this comment.
Hi @alicejw-aws , can you please update the name of the PR to match our naming standards? This will appear in the release notes and should follow a similar convention. Thanks!
Signed-off-by: alicejw <alicejw@amazon.com>
Naarcha-AWS
left a comment
There was a problem hiding this comment.
@natebower can verify, but I believe that "Trace Analytics" should be lowercased in most instances.
Otherwise, looks good to me.
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
…. 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>
|
Doc review updates completed. Sending for editorial review. |
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
|
Updated PDF after adding additional step from eng. |
natebower
left a comment
There was a problem hiding this comment.
@alicejw-aws Please see my comments and changes and let me know if you have any questions. Thanks!
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
Signed-off-by: alicejw <alicejw@amazon.com>
* 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>
Signed-off-by: alicejw alicejw@amazon.com
Description
New doc for how to use Jaeger trace data for analytics.
Issues Resolved
#2313
PDF for reviewers
To see the document as it will be rendered on the site, take a look at this PDF.
Analyze Jaeger trace data - OpenSearch documentation.pdf
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.