Diagnostics CLI (nrdiag) release notesRSS

Changes

Base

• Base/Collector/ConnectUS - Updated to check the connection using https://collector.newrelic.com/jserrors/ping instead of mongrel
• Base/Collector/ConnectEU - Updated to check the connection using https://collector.eu.newrelic.com/jserrors/ping instead of mongrel
• Base/Collector/ConnectTLS - New task that uses https://connection-test.newrelic.com to confirm the host is connecting with TLS 1.2

.NET APM Agent

• Dotnet/Profiler/TLSRegKey - New task to confirm the TLS related registry settings for .NET are set correctly for TLS 1.2 per this document

Infrastructure

• Infra/Agent/Version - Updated to check the release date of the installed agent version and report a failure if it is an unsupported version
• Infra/Agent/Connect - Updated to check the full list of domains listed in here

Changes

• Infra/Log/Collect and Infra/Log/LogLevelCheck - Updated to support new configuration options available for the Infrastructure agent
• DotNetCore/Agent/Installed - Updated to support new install location of the .NET agent
• DotNetCore/Env/Versions - Updated to use dotnet --info for determine what versions of .NET Core are installed. If that fails, it will fall back on dotnet --version, then if both of those commands fail, it will look for the .NET Core installation directories

Changes

New Relic APM

• PHP/Agent/Version - updates warning if there are multiple versions

Operating System

• Builds for arm64

Bug Fixes

• Upload process optimized

New Feature

• -include command line flag
  • Specify a file or directory to include in the nrdiag-output.zip file. You can use relative or absolute paths. Use this along with -attach to upload the file(s) to your New Relic account.
  • Example usage: ./nrdiag -include ./path/to/file
  • Read more here!

Changes

Attachments

• Deprecated command line flag -attachment-key for automatic upload to a support ticket. Please use the -attach flag to upload to your New Relic account instead. Data uploaded with -attach can be viewed here: https://one.newrelic.com/diagnostics-cli-output

Changes

Attachments

• Command line flag -a or -attachment-key is now -ak or -attachment-key
• New command line flag -a or -attach needs no arguments to be supplied to it
  • Uploads Diagnostics output to a New Relic account
• Removed command line flag -file-upload for arbitrary single files uploads
• All output is uploaded to S3 if specified with -attach or -attachment-key

New Relic APM

• Node/Env/Versions - Node 10 is no longer compatible with New Relic Node.js Agents 8.0.0.0 and above

Bug Fixes

• Infra/Config/IntegrationsValidateJson - JSON validation of OHIS is now compatible with the new and old format for validation of OHIS

Changes

• Node/Config/Agent - Checks for configuration by environment variables
• Base/Config/Collect - Report secure files rejected for collection in task summary
• Base/Config/ValidateLicenseKey - Gives warning instead of failure in case its an ingest key
• Attachments - Fix issue where automatic attachments to support tickets would fail
• Task Errors Now provide guidance on where to report them

New

• Base/Log/Copy - It will check for the .NET log files path by looking into NEWRELIC\_PROFILER\_LOG\_DIRECTORY and NEW\_RELIC\_LOG environment variables.
• Browser/Agent/GetSource - This validation will now detect when the browser script is not in the head tag

Changes

• Dotnet/Env/Target - Now validates .NET agent is compatible with versions 4.8 and 5.0 for .NET framework.
• Java/JVM/VendorsVersions - It will validate open JDK 7.15 and HotSpot 7.15

New

• Diagnostics CLI will validate the Java agent configuration that has been done through Java System Properties.
• Infra/Env/NrjmxBeans - Validates that the mbeans that the user wants to query with the New Relic JMX integration are available for the integration to pull from. This task is available for Linux and Windows.
• Infra/Env/ValidateZookeeperPath - Validates that the setting for zookeeper_path (found in kafka-config.yml) is a valid path for the New Relic Kafka integration.

Bug fixes

• Java/Env/Process - This task validates that the New Relic Java agent jar has been correctly added to the -javavagent argument. However, previously, it would only validate those jars that were explicitly named newrelic.jar. We have changed that behavior to look for a jar that could include that version in the filename.
• Infra/Config/ValidateJMX - The nrdiag-output.json will include information about the Java version and non-sensitive command line arguments for JMX. This data is mainly relevant for Support troubleshooting. Additionally, this health check now can run on Windows.
• Java/JVM/Permissions - It will not validate permissions for a log path that has been commented out from the Java agent config file.
• Infra/Config/IntegrationsMatch - This validation will no longer require the presence of on-host integration (OHI) definitions files when the user has an infrastructure agent 1.8.0 or newer and the OHI config file is using the newer configuration format.

Changes

• The product will now be known as Diagnostics CLI
• Diagnostics CLI is proud to announce that is codebase is now part of New Relic's Open Source Community: https://github.com/newrelic/newrelic-diagnostics-cli