-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix: infra-agent settings in beanstalk docs #15014
fix: infra-agent settings in beanstalk docs #15014
Conversation
Hi @josemore 👋 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. Gatsby Cloud will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 20 to 30 minutes). |
✅ docs-website-develop deploy preview ready
|
|
||
<Collapser id="linux" title="Linux"> | ||
|
||
1. **Resolve the domain:** Use nslookup or dig to validate that the Linux system can resolve the domain to an IP address: |
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.
1. **Resolve the domain:** Use nslookup or dig to validate that the Linux system can resolve the domain to an IP address: | |
1. **Resolve the domain:** Use `nslookup` or `dig` to validate that the Linux system can resolve the domain to an IP address: |
|
||
Analyze the output to identify potential network issues, such as high latency or packet loss. | ||
|
||
4. **Curl:** Use curl to check if the endpoint is reachable: |
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.
4. **Curl:** Use curl to check if the endpoint is reachable: | |
4. **Curl:** Use `curl` to check if the endpoint is reachable: |
|
||
## Troubleshoot with NRDiag | ||
|
||
[Code Implementation](https://github.com/newrelic/newrelic-diagnostics-cli/blob/main/tasks/infra/agent/connect.go#L48) |
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.
@josemore What's the purpose of this link? Can you add something before this link, like what readers would expect to see from this link or why they'd want to go to it?
See https://docs.newrelic.com/docs/new-relic-solutions/get-started/networks/#infrastructure for more information. | ||
``` | ||
|
||
Note that the nrdiag Connect task result is shown in stdout, it should be collected with the `nrdiag_output.zip` file. |
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.
Note that the nrdiag Connect task result is shown in stdout, it should be collected with the `nrdiag_output.zip` file. | |
Note that the `nrdiag Connect` task result is shown in `stdout`, but it should be collected with the `nrdiag_output.zip` file. |
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.
See my comments
thanks @ally-sassman, I removed the "network troubleshooting" doc from this PR, I'll submit that one later this week (and already incorporated your feedback). |
Give us some context