-
Notifications
You must be signed in to change notification settings - Fork 504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds Jaeger trace data for analytics documentation #2374
Conversation
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
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 <[email protected]>
Tech review comments are now incorporated. (except need one more command from @derek-ho ) Thanks |
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Updated PDFs after final clarification meeting and small updates. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alicejw-aws Made some comments and suggestions. Good work!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@natebower can verify, but I believe that "Trace Analytics" should be lowercased in most instances.
Otherwise, looks good to me.
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
…. 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 <[email protected]>
Doc review updates completed. Sending for editorial review. |
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Updated PDF after adding additional step from eng. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alicejw-aws Please see my comments and changes and let me know if you have any questions. Thanks!
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw <[email protected]>
* for new page how to analyze Jaeger trace data Signed-off-by: alicejw <[email protected]> * remove old image Signed-off-by: alicejw <[email protected]> * for new information and doc writer checklist Signed-off-by: alicejw <[email protected]> * for new information and doc writer checklist Signed-off-by: alicejw <[email protected]> * small rewrite Signed-off-by: alicejw <[email protected]> * new clean images from Dashboards URL directly Signed-off-by: alicejw <[email protected]> * for additional information Signed-off-by: alicejw <[email protected]> * remove blank lines Signed-off-by: alicejw <[email protected]> * for tech review feedback updates Signed-off-by: alicejw <[email protected]> * add requirements section Signed-off-by: alicejw <[email protected]> * for new procedure Signed-off-by: alicejw <[email protected]> * for tech review feedback updates Signed-off-by: alicejw <[email protected]> * continued updates Signed-off-by: alicejw <[email protected]> * for docker compose file instructions Signed-off-by: alicejw <[email protected]> * for docker usage instruction Signed-off-by: alicejw <[email protected]> * for step 2 view dashboards Signed-off-by: alicejw <[email protected]> * for additional link provided in tech review Signed-off-by: alicejw <[email protected]> * for link to index page to introduce the feature Signed-off-by: alicejw <[email protected]> * final checklist Signed-off-by: alicejw <[email protected]> * add warning not to use sample file in prod env Signed-off-by: alicejw <[email protected]> * updated docker file that is safe for prod env, remove warning note for previous file Signed-off-by: alicejw <[email protected]> * for small update to parent page Signed-off-by: alicejw <[email protected]> * for tech review Signed-off-by: alicejw <[email protected]> * typo fix for font Signed-off-by: alicejw <[email protected]> * for doc review #1 feedback updates Signed-off-by: alicejw <[email protected]> * for doc review feedback #2 updates Signed-off-by: alicejw <[email protected]> * for a couple minor changes Signed-off-by: alicejw <[email protected]> * 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 <[email protected]> * need to add additional step from eng to generate sample data Signed-off-by: alicejw <[email protected]> * for additional step image of sample app Signed-off-by: alicejw <[email protected]> * rename step numbers Signed-off-by: alicejw <[email protected]> * minor fix heading levels Signed-off-by: alicejw <[email protected]> * updates recommended by the editorial reviewer Signed-off-by: alicejw <[email protected]> * clarify Spans window function Signed-off-by: alicejw <[email protected]> * clarified individual trace details section Signed-off-by: alicejw <[email protected]> Signed-off-by: alicejw <[email protected]>
Signed-off-by: alicejw [email protected]
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.