• EnglishEspañol日本語한국어Português
  • Inicia sesiónComenzar ahora

Diagnostics CLI (nrdiag) release notesRSS

April 6, 2020
Diagnostics CLI (nrdiag) v1.8.28

New Checks

  • Synthetics/Minion/CollectLogs - Collect logs of found Containerized Private Minions
  • Infra/Env/ClockSkew - Detect if host has clock skew from New Relic collector

Changes

  • Increase scope of Python/Requirements/PythonVersion 's ability to detect Python version supportability with New Relic Python Agents
  • Infra/Config/ValidateJMX is incompatible with Windows environments and will no longer run when New Relic Diagnostics is run in Windows
  • Base/Log/Copy will no longer return "Success", but a instead a "Warning", when only stdout/stderr logging is detected
  • Base/Env/HostInfo expanded to collect kernel version, cpu, and memory information

February 3, 2020
Diagnostics CLI (nrdiag) v1.7.27

New Feature

  • Task Suites
    • Collection of tasks that target a specific NR Product or issue
    • Example usage for java agent: ./nrdiag --suites java
    • Read more here!

Changes

  • Improve error messaging when there is an issue uploading support ticket attachments
  • Improve detection and usage of proxies configured for installed New Relic products
  • Always collect latest New Relic log file, regardless of file age
  • Detected Node.js application NPM packages are now visible nrdiag-output.json
  • Fixed bug where Infra/Log/Collect would report "Success" when no New Relic Infrastructure log file path was configured
  • Improve messaging when New Relic configuration files are not detected on system

January 6, 2020
Diagnostics CLI (nrdiag) v1.6.26

Changes

  • New Relic Diagnostics installation zip now includes 64 bit binary for Mac OS.
  • New Relic Infrastructure log collection now supports latest New Relic Infrastructure agent.
  • Output of Infra/Config/ValidateJMX, when saved in nrdiag-output.json or nrdiag-otuput.zip, no longer contains JMX server credentials.
  • Java/Config/Validate now has clearer help/explanation verbiage.
  • When a New Relic Java agent configuration file is detected, Java/Env/Process now validates that there is at least one running java process that includes the New Relic Java agent flag.
  • New Relic Diagnostics now uses the diagnostics.service.newrelic.com host for uploading support ticket attachments (when applicable), instead support.newrelic.com.

December 5, 2019
Diagnostics CLI (nrdiag) v1.6.25

New diagnostic checks

  • Base/Config/AppName - Check for default application names in New Relic agent configuration

Changes

  • The following tasks have been updated to support their latest agent versions
    • DotNet/Agent/Installed
    • DotNet/Profiler/WasRegKey
    • DotNet/Profiler/W3svcRegKey
    • DotNetCore/Agent/Installed
  • DotNet/Profiler/EnvVarKey now provides clearer instructions when an issue is detected
  • Infra/Agent/Debug can now enable New Relic Infrastructure agent debug logging on Windows Infrastructure agents 1.7.0 and above
    • Linux: ./nrdiag -t Infra/Agent/Debug -a ATTACHMENT_KEY
    • Windows: .\nrdiag.exe -t Infra/Agent/Debug -a ATTACHMENT_KEY
    • Windows-x64: .\nrdiag_x64.exe -t Infra/Agent/Debug -a ATTACHMENT_KEY
  • Python/Requirements/PythonVersion now correctly determines Python version supportability in line with the New Relic Python agent
  • New Relic Diagnostics now uses compression to produce a very light weight nrdiag-output.zip

October 22, 2019
Diagnostics CLI (nrdiag) v1.5.24

Changes

  • Changed Infrastructure agent debug log collection to wait 3 minutes instead of 5 minutes
  • Added user prompt before collection of Infrastructure on-host integration configuration files
  • Updated diagnostic check explanation verbiage to be more consistent
  • Updated collection of Node.js application dependencies to ignore some errors

September 26, 2019
Diagnostics CLI (nrdiag) v1.5.23

New Diagnostic Checks

New Relic Infrastructure

  • Infra/Agent/Debug - Enable debug logging for Infrastructure Agent on non-Windows environments

Changes

  • docker info output now collected for troubleshooting
  • Validate support ticket attachment key length
  • Improve messaging when upload to support ticket fails
  • Update supported Python web frameworks to match current Python agent
  • Update supported Java JVMs to match current Java agent
  • Infrastructure logs now also collected from the path in NRIA_LOG_FILE env variable

August 16, 2019
Diagnostics CLI (nrdiag) v1.5.22

New Diagnostic Checks

New Relic APM

  • Node/Env/Dependencies - Detect Node.js modules by running npm ls

Synthetic monitors

  • Synthetics/Minion/DetectCPM - Check for and inspect instances of the Containerized Synthetics Private Minion

Bug fixes

  • Fixed bug where empty New Relic license keys were not flagged as invalid
  • Fixed bug where some override options using -o flag were not being honored
  • Fixed bug where EOL status could not be determined when multiple Ruby agents detected
  • Redact HTTP_PROXY environment variable when detected at run time

July 26, 2019
Diagnostics CLI (nrdiag) v1.5.21

Bug fixes

  • Fixed a bug where the Java Agent version was being improperly parsed for some older Agents

July 23, 2019
April 23, 2019
Diagnostics CLI (nrdiag) v1.4.19

New diagnostic checks

New Relic APM

  • Node/Env/VersionCompatibility - Check Node.js version compatibility with the New Relic Node Agent.

Bug fixes

  • Fixed a bug where some Infrastructure on-host integration config and definition file paths were being incorrectly flagged.
  • On-host integration config sample files are now ignored.
  • Fixed a bug where archived logs were being collected for some system directories.

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.