Skip to content

Commit

Permalink
Update run-diagnostics-cli-nrdiag.mdx
Browse files Browse the repository at this point in the history
  • Loading branch information
cade-conklin committed Oct 6, 2021
1 parent 09ae728 commit 6caff50
Showing 1 changed file with 13 additions and 11 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -42,13 +42,13 @@ To run the Diagnostics CLI, follow the procedures for your platform:
* [Manually download the latest version](https://download.newrelic.com/nrdiag/nrdiag_latest.zip).
2. Unzip `nrdiag.zip` if necessary.
3. From the `nrdiag_1.2.3/linux` directory, move `nrdiag` into the application's root directory.
4. Run `nrdiag` (along with any [CLI options](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) and/or a [ticket attachment key](#attach-ticket-results)):
4. Run `nrdiag` (along with any [CLI options](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag)

```
./nrdiag <var>CLI_OPTIONS</var>
```

The Diagnostics CLI outputs any issues it discovers, and uploads relevant files to your New Relic Support ticket if you include a ticket attachment key.
The Diagnostics CLI outputs any issues it discovers, and uploads relevant files to your New Relic Account if you include an attachment flag.
</Collapser>

<Collapser
Expand All @@ -63,13 +63,13 @@ To run the Diagnostics CLI, follow the procedures for your platform:
* [Manually download the latest version](https://download.newrelic.com/nrdiag/nrdiag_latest.zip).
2. Unzip `nrdiag.zip` if necessary.
3. From the `nrdiag_1.2.3/mac` directory, move `nrdiag` into the application's root directory.
4. Run `nrdiag` (along with any [CLI options](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) and/or a [ticket attachment key](#attach-ticket-results)):
4. Run `nrdiag` (along with any [CLI options](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag)

```
./nrdiag <var>CLI_OPTIONS</var>
```

The Diagnostics CLI outputs any issues it discovers, and uploads relevant files to your New Relic Support ticket if you include a ticket attachment key.
The Diagnostics CLI outputs any issues it discovers, and uploads relevant files to your New Relic Account if you include an attachment flag.
</Collapser>

<Collapser
Expand Down Expand Up @@ -194,10 +194,14 @@ To upload your results automatically to a New Relic Account when the Diagnostics

Uploading your results to an account will automatically upload the contents of the `nrdiag-output.json` and `nrdiag-output.zip`. If you want to inspect or modify the file's contents before upload, follow the manual upload procedures.

<Callout variant="important">
If there is an issue with your license key you will need to manually upload results to your account.
</Callout>

**Linux, macOS, synthetic private minion:**

```
./nrdiag -attachment-key <var>ATTACHMENT_KEY</var>
./nrdiag -attach
```

**Windows:**
Expand All @@ -207,18 +211,16 @@ To run from PowerShell, add `./` to the start of `cmd`.
* For 32-bit systems:

```
nrdiag.exe -attachment-key <var>ATTACHMENT_KEY</var>
nrdiag.exe -attach
```
* For 64-bit systems:

```
nrdiag_x64.exe -attachment-key <var>ATTACHMENT_KEY</var>
nrdiag_x64.exe -attach
```

### Manual upload [#manual]

If you modified or inspected the content of `nrdiag-output.zip` and want to attach it to a support ticket, you can use the `-file-upload` and `-attachment-key` command line flags together to upload a specific file:
If you have a Support Ticket, use the permalink functionality to share your results. This will help improve troubleshooting speed.
The New Relic Diagnostics App has the drag and drop functionality if your results are unable to be automatically uploaded.

```
./nrdiag -attachment-key <var>ATTACHMENT_KEY</var> -file-upload <var>ZIP_FILENAME</var>
```

0 comments on commit 6caff50

Please sign in to comment.