Like any other New Relic tool, the Diagnostics CLI service is designed to protect data privacy for you and your customers. The Diagnostics CLI inspects system information and relevant New Relic product artifacts, such as logs and config files. The CLI focuses only on information needed to perform diagnostic checks that assess New Relic product configuration and operability.
By default, this data is not transmitted to New Relic. You do have the option to upload this information to your New Relic account over HTTPS. For more information about New Relic's security measures, see our security and privacy documentation, or visit the New Relic security website.
The use of the Diagnostics CLI is subject to this license agreement, as well as licensing agreements for open-source software used by the Diagnostics CLI.
The Diagnostics CLI allows uploading of this information to a New Relic account over HTTPS if you use a specific command-line argument. You will be prompted before the collection of any files that we expect to have sensitive information.
Before the collected files contained within
nrdiag-output.json are uploaded to New Relic, you will also be prompted. This allows you to review and edit any information that you do not want to provide. (For example, the
nrdiag-output.zip will include your user name.) You also have the option to cancel the upload altogether.
All attachments made using
nrdiag or containing
nrdiag data are stored by New Relic.
The Diagnostics CLI examines the following environment variables to perform diagnostic checks. The values of these variables are recorded locally in the
nrdiag-output.json file. These include:
- Any environment variable containing
- Any environment variable beginning with