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

Refactor distributed tracing instructions #17928

Merged
merged 10 commits into from
Aug 1, 2024

Conversation

rhetoric101
Copy link
Contributor

This is for NR-283802. For all APM agents:

  • Remove section for old agents.
  • Remove headings about old an new agents.
  • Replace old manual steps with the <Steps> component.

@rhetoric101 rhetoric101 added content requests related to docs site content from_tw Identifies issues/PRs from Tech Docs writers labels Jul 8, 2024
@rhetoric101 rhetoric101 self-assigned this Jul 8, 2024
Copy link

github-actions bot commented Jul 8, 2024

Hi @rhetoric101 👋

Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days.

We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes).

Copy link

netlify bot commented Jul 8, 2024

Deploy Preview for docs-website-netlify ready!

Name Link
🔨 Latest commit 3e782d6
🔍 Latest deploy log https://app.netlify.com/sites/docs-website-netlify/deploys/66aaae1fed3edd0008fc3757
😎 Deploy Preview https://deploy-preview-17928--docs-website-netlify.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@rhetoric101 rhetoric101 marked this pull request as ready for review July 16, 2024 22:26
@rhetoric101 rhetoric101 marked this pull request as draft July 16, 2024 22:27
@rhetoric101 rhetoric101 marked this pull request as ready for review July 16, 2024 22:51
@github-actions github-actions bot requested a review from akristen July 16, 2024 22:51
@paperclypse paperclypse requested review from nbaenam and removed request for akristen July 22, 2024 15:14
nbaenam
nbaenam previously approved these changes Jul 23, 2024
Copy link
Contributor

@nbaenam nbaenam left a comment

Choose a reason for hiding this comment

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

Hey @rhetoric101, wow, you did a lot of work here! I seem to have added a lot of comments, but they are more or less the same for all files, but I've repeated them so as not to forget them. Feel free to take them or leave them🙂


### Set up Infinite Tracing [#infinite-tracing]
## Infinite Tracing [#infinite-tracing]

Standard distributed tracing for APM agents ([above](#quick-start-apm)) captures up to 10% of your traces, but if you want us to analyze all your data and find the most relevant traces, you can set up Infinite Tracing.
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd remove the above link and added to the Standard distributed tracing for APM agents text.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@nbaenam I fixed this!


### Set up Infinite Tracing [#infinite-tracing]
## Infinite Tracing [#infinite-tracing]

Standard distributed tracing for APM agents ([above](#quick-start-apm)) captures up to 10% of your traces, but if you want us to analyze all your data and find the most relevant traces, you can set up Infinite Tracing.
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd remove the above link and added to the Standard distributed tracing for APM agents text.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@nbaenam I fixed this!

@@ -125,17 +120,21 @@ Standard distributed tracing for APM agents ([above](#quick-start-apm)) captures
To learn more about this feature, see [Infinite Tracing](/docs/understand-dependencies/distributed-tracing/infinite-tracing/introduction-infinite-tracing).
Copy link
Contributor

Choose a reason for hiding this comment

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

The same as the others. I'd remove this tip and add the link directly to Infinite Tracing.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@nbaenam I fixed this!

The Infinite Tracing setup builds on standard distributed tracing. So, make sure you've completed the [steps above](#quick-start-apm), and then continue with the trace observer setup.
</Step>
<Step>
### Set up the trace observer [#provision-trace-observer]

The trace observer is a New Relic AWS-based service that collects and analyzes all your traces. Follow the instructions in <a href="/docs/understand-dependencies/distributed-tracing/infinite-tracing/set-trace-observer" target="_blank">Set up trace observer</a>. When you're done, return here with your trace observer information and continue with the next step to configure the agent.
Copy link
Contributor

Choose a reason for hiding this comment

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

Here there is another HTML structure for URL.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@nbaenam Good catch! I fixed this!

@@ -54,8 +47,9 @@ To start the installation routine, click the tile below. When you're finished in
icon={<img src={apmPython} alt="Python"/>}
/>
Copy link
Contributor

Choose a reason for hiding this comment

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

The same as the other with the Start installation text below the tile.

@@ -45,7 +45,7 @@ Figure out which services touch your request so you can instrument each of them
For each service involved in your transactions, you'll perform separate installations of the agent. If some of your services use other languages, simply repeat the [installation steps](/docs/distributed-tracing/enable-configure/quick-start) for those languages.

<Callout variant="tip">
The Go agent requires you to manually instrument your Go services, unlike the auto-instrumentation of the other New Relic agents. This means you need to add some lines to your code to use the Go agent.
The Go agent requires you to manually instrument your Go services, unlike the auto-instrumentation of the other New Relic agents. This means you need to add some lines to your code to use the Go agent. You'll learn about this when you start the installation below.
Copy link
Contributor

@paperclypse paperclypse Jul 31, 2024

Choose a reason for hiding this comment

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

@rhetoric101 Do we want to clarify how or why they'll learn more about this? Is there something in the installation process itself that helps people learn more? Do we just describe more fully later in this doc? I think it might be good to clarify.

The more I think about this tip, the more skeptical I am that we need it at all. Wouldn't it make more sense to put this with the Go installation steps directly?

My baseline assumption here is that someone is starting with a Go application that they want to monitor, not that they're trying to decide what language to use to build an app to monitor.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@paperclypse the goal here is to just give users a heads-up in case they expect auto-instrumentation. They'll find out soon enough when they start, but I'd like to leave this in.

Copy link
Contributor

Choose a reason for hiding this comment

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

OK, I'll defer to you here

paperclypse
paperclypse previously approved these changes Jul 31, 2024
Copy link
Contributor

@paperclypse paperclypse left a comment

Choose a reason for hiding this comment

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

I just looked at your last commit, post @nbaenam's review. I left a comment there. Basically, I'm wondering if that's the best place to leave the tip or even if we need it at all.

Copy link
Contributor

@paperclypse paperclypse left a comment

Choose a reason for hiding this comment

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

Links all look good

@rhetoric101 rhetoric101 merged commit d0c63bc into develop Aug 1, 2024
20 checks passed
@rhetoric101 rhetoric101 deleted the rhs-remove-old-dt-sections branch August 1, 2024 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content requests related to docs site content from_tw Identifies issues/PRs from Tech Docs writers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants