Diagnostics CLI (nrdiag) release notesRSS

Improvements

• DotNet/Agent/Installed: Updated the task to detect .NET agent DLLs when newrelic.config is absent, and enabled case-insensitive matching for newrelic.config. Previously, a missing configuration file prevented agent detection and skipped downstream .NET tasks (#276).
• DotNet/Config/Agent: Updated the task to issue a warning rather than a failure when newrelic.config is missing (#276).
• .NET Core configuration: Updated file collection to gather and analyze environment-specific configuration files (such as appsettings.Production.json). Unrelated files with similar naming patterns (such as myappsettings.json) are no longer collected (#276).
• .NET Core custom instrumentation: Updated XML reader tasks to inspect the agent extensions and extensions/netcore directories, aligning with profiler file-resolution logic (#276).
• .NET agent logs: Updated log filtering so the 1-day cutoff applies exclusively to profiler logs, preserving agent logs from the preceding 7 days. Profiler logs now also respect the -lastModifiedDate flag (#276).
• .NET agent version and EOL checks: Updated end-of-life (EOL) and supported version parameters for the .NET agent. Added discrete detection for .NET Framework versions 4.7.1, 4.7.2, 4.8, and 4.8.1, and enabled version collection for the .NET Core agent (#273).
• .NET agent log level: Updated log level configurations to evaluate settings case-insensitively, matching the .NET agent runtime behavior (#274).
• .NET TLS check: Updated registry validation so a missing SchUseStrongCrypto key is no longer flagged as an error, as supported .NET Framework versions default to TLS 1.2 when the key is absent. An error is now reported only when the key exists and is set to a value other than 1 (#275).

Bug fixes

• Fixed an issue where uploads to the Japan data region failed due to an unassigned upload URL in release builds (#277).
• Fixed an issue in .NET Framework profiling environment variable validation to correctly check COR_ENABLE_PROFILING. Added support for both NEW_RELIC_LOG_DIRECTORY and NEWRELIC_LOG_DIRECTORY when resolving .NET agent log locations (#272).
• Fixed an issue where environment variable values containing equal signs (=) were truncated during parsing (#272).

Task Updates

• K8s/AgentControl/Logs - Updated to collect all log lines (#267).

New Feature

• We have added a new suite and the following tasks for Agent Control (#268):
  • onhost-agent-control suite - Gathers information about agent-control logs, status, connectivity, and resources on the host. To use it, run nrdiag -suites onhost-agent-control.
  • AgentControl/Config/Agent - Detects agent-control via PATH, known install paths, and data directory fallback; collects all YAML files from fleet-data and local-data, preserving the original directory structure for all registered sub-agents
  • AgentControl/Config/DirTree - Writes a formatted directory tree of all agent-control installation paths to the zip for structure inspection
  • AgentControl/Agent/Connect - Checks TCP/TLS reachability of the OpAMP, JWKS, and OAuth2 token endpoints (reading URLs from local_config.yaml); validates that the local identity private key is a readable, parseable PKCS8 key (RSA, Ed25519, or ECDSA)
  • AgentControl/Agent/Logs - On Linux, collects logs via journalctl -u newrelic-agent-control; on Windows, globs all date-rotated *.newrelic-agent-control.log files from the default log directory
  • AgentControl/Agent/StatusServer - Queries the local status server at the host/port configured in local_config.yaml (default 127.0.0.1:51200) and saves the JSON response to the diagnostics zip

New features

• The Diagnostics CLI now supports New Relic's Japan data region. If your account is in the Japan region, specify the region flag when running the CLI (#263):

  bash

  Copy

  $
  ./nrdiag -region JP

  The region flag accepts US, EU, or JP (case insensitive) and defaults to US.

Dependency updates

• Updated golang.org/x/net from 0.33.0 to 0.55.0 (#264).

Fixes

• Sensitive values such as License Keys and passwords are now obfuscated in all task outputs including in the JSON file and any config files that are collected (#260).

Task Updates

• Updated Infra/Agent/Connect to handle additional success responses from the endpoints (#260).

Fix

• Update supported versions for .NET, Ruby, Python and Node.JS APM agents (#258).

Fixes

• Fixed Java config panic (#255).
• Obfuscated API key in output (#252).

Fix

• GLIBC related errors such as /lib64/libc.so.6: version 'GLIBC_2.34' not found have been resolved (#252).

Task Updates

• Update the Java/Appserver/JbossEapCheck version compatibility check (#251).

New Task

• K8s/AgentControl/agent-control-install-job-logs - Collects logs generated by the agent-control installation

Task Updates

• A new command line option -ac-agents-namespace was added for specifying a namespace for Agent Control agents (#243). The following tasks have been updated to use the new namespace:
  • K8s/Resources/Config
  • K8s/Resources/Daemonset
  • K8s/Resources/Deploy
  • K8s/Resources/Pods

Fixes

• GLIBC related errors such as /lib64/libc.so.6: version 'GLIBC_2.34' not found have been resolved (#244).