Diagnostics CLI (nrdiag) release notesRSS

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

New Checks

• Base/Java/ValidateSettings - Performs type validation of the values provided in the Java agent configuration file.

Changes

• Base/Env/SELinux - This check is now included in the minion suite of tasks with the command flag -suites minion.
• Base/Config/Validate - It will now validate a config file that a customer has collected using command flag -config-file.

New Checks

• Base/Env/SELinux - Check the presence and state for SELinux
• Base/Config/ValidateLicenseKey - Validate license keys found in agent configuration files and environment variables.
• Base/Config/ValidateHSM - Validates high-security mode local agent configuration files and environment variable against account configuration.
• Ruby/Requirements/Version - Check Ruby agent version compatibility with environment's Ruby version

Changes

• Base/Config/Collect - Now checks New Relic environment variables that are used to specify a custom agent config path.
• Base/Config/Collect - Check for custom agent config paths in .NET web.config or app.config files.
• Base/Log/Copy - Fix issue where log files can be collected twice when New Relic log path environment variables are used.
• Base/Config/LicenseKey - Will now warn if multiple unique license keys are detected in different agent configurations.
• Node/Config/Agent - Fix issue where a Node agent would be reported multiple times in detection.
• Java/Env/VendorsVersions - Now it can run for Windows environment.

New Checks

• Base/Env/Azure it checks if the customer is running Diagnostics on an Azure environment
• Node/Env/NPMPackage collects package.json and package-lock.json for the customer's app
• Node/Requirements/ProblematicModules will declare incompatible modules such as babel and Mongoose to let the customer know they may run into "missing data" issues

Changes

• Base/Log/Copy now collects log files specified in New Relic config files
• Base/Config/AppName now correctly parses arrays of applications names
• Base/Config/Collect no longer collects config files found in /node_modules
• PHP/Daemon/Running changed payload
• Base/Log/ReportingTo payload now only includes log files containing reporting to lines. Also sanitizes RPM urls sent in responses from the NR collector
• Java/JVM/Version has been renamed to Java/Env/Version
• Java/JVM/Version now supports HotSpot/OpenJDK 14
• DotNet/Requirements/DotnetTarget as been renamed to DotNet/Env/TargetVersion
• Base/Env/DotNetCoreVersions has been renamed to DotNetCore/Env/Versions
• Base/Env/DotnetVersions has been renamed to DotNet/Env/Versions
• Infra/Agent/Connect now performs a connection check to the collector endpoint for the detected region
• Fixed bug in Windows where NR Diag would incorrectly flag valid task suites, as invalid

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

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

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.

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

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