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

fix: infra-agent settings in beanstalk docs #15014

Merged

Conversation

josemore
Copy link
Contributor

Give us some context

  • Add a section to the infra agent Beanstalk installation instructions explaining how to configure the agent.

@github-actions
Copy link

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).

@github-actions github-actions bot added this to Hero to triage in Docs PRs and Issues Oct 30, 2023
@gatsby-cloud
Copy link

gatsby-cloud bot commented Oct 30, 2023

✅ docs-website-develop deploy preview ready

@ally-sassman ally-sassman added content requests related to docs site content from_internal Identifies issues/PRs from Relics (except writers) labels Oct 30, 2023

<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:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
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:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
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)
Copy link
Contributor

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.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
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.

Copy link
Contributor

@ally-sassman ally-sassman left a comment

Choose a reason for hiding this comment

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

See my comments

@ally-sassman ally-sassman moved this from Hero to triage to Waiting on TW to merge in Docs PRs and Issues Oct 30, 2023
@ally-sassman ally-sassman moved this from Waiting on TW to merge to Waiting on SME/Blocked in Docs PRs and Issues Oct 30, 2023
@josemore
Copy link
Contributor Author

josemore commented Oct 31, 2023

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).

@ally-sassman ally-sassman merged commit 0425181 into newrelic:develop Oct 31, 2023
9 of 10 checks passed
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_internal Identifies issues/PRs from Relics (except writers)
Projects
Docs PRs and Issues
Waiting on SME/Blocked
Development

Successfully merging this pull request may close these issues.

None yet

2 participants