Diagnostics release notes

Diagnostics release notes

Saturday, August 1, 2020 - 09:30

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`.
Tuesday, July 14, 2020 - 08:45

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.
Monday, May 18, 2020 - 08:30

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
Monday, April 6, 2020 - 15:00

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
Monday, February 3, 2020 - 15:00

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 NodeJS 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
Monday, January 6, 2020 - 10:30

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.
Thursday, December 5, 2019 - 15:15

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

Tuesday, October 22, 2019 - 09:45

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 NodeJS application dependencies to ignore some errors

Thursday, September 26, 2019 - 13:45

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
Friday, August 16, 2019 - 13:45

New Diagnostic Checks

New Relic APM

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

New Relic Synthetics

  • 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

Pages