Skip to content
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

Add Otel Java links to readme. Update CI badge. #339

Merged
merged 4 commits into from
Jun 29, 2022

Conversation

srprash
Copy link
Contributor

@srprash srprash commented Jun 28, 2022

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@srprash srprash requested a review from a team as a code owner June 28, 2022 20:25
@codecov-commenter
Copy link

codecov-commenter commented Jun 28, 2022

Codecov Report

Merging #339 (370ad20) into master (e3436c1) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #339   +/-   ##
=========================================
  Coverage     58.96%   58.96%           
  Complexity     1207     1207           
=========================================
  Files           131      131           
  Lines          5064     5064           
  Branches        592      592           
=========================================
  Hits           2986     2986           
  Misses         1805     1805           
  Partials        273      273           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e3436c1...370ad20. Read the comment docs.

@srprash srprash changed the title Add Otel Java links to readme Add Otel Java links to readme. Update CI badge. Jun 28, 2022
Copy link
Contributor

@jj22ee jj22ee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm 🚢

Copy link
Contributor

@NathanielRN NathanielRN left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just wanted to make it clear that OpenTelemetry is the preferred method!

srprash and others added 2 commits June 28, 2022 20:24
Co-authored-by: Nathaniel Ruiz Nowell <[email protected]>

### :mega: OpenTelemetry Java with AWS X-Ray

AWS X-Ray recommends using AWS Distro for OpenTelemetry (ADOT) to instrument your application due to its wider range of features and instrumentations. See [Working with Java](https://docs.aws.amazon.com/xray/latest/devguide/xray-java.html) for more help with choosing between ADOT and X-Ray SDK.
Copy link
Contributor

@NathanielRN NathanielRN Jun 29, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it’s useful to add this? I find that customers often think they need both when they only need one.

Suggested change
AWS X-Ray recommends using AWS Distro for OpenTelemetry (ADOT) to instrument your application due to its wider range of features and instrumentations. See [Working with Java](https://docs.aws.amazon.com/xray/latest/devguide/xray-java.html) for more help with choosing between ADOT and X-Ray SDK.
AWS X-Ray recommends using AWS Distro for OpenTelemetry (ADOT) to instrument your application **instead of this X-Ray SDK** due to its wider range of features and instrumentations. See the [AWS X-Ray docs on Working with Java](https://docs.aws.amazon.com/xray/latest/devguide/xray-java.html) for more help with choosing between ADOT and X-Ray SDK.

@srprash srprash merged commit a9ec225 into aws:master Jun 29, 2022
@srprash srprash deleted the readme_otel branch June 29, 2022 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants