.NET agent release notesRSS

Fixes

• Allow StackExchange.Redis v2+ profiling to start outside of a transaction. (#1501) (#1504) (925d016)
• Allow the agent to accept multiple versions of legacy NR distributed tracing headers. (#1489) (23ee241)
• Fix a memory leak when using StackExchange.Redis v2+. (#1473) (#1504) (925d016)
• Retry connection on HttpRequestException error. (#1514) (#1484) (99b520e)

Once published, you can find the release artifacts for this release here or on NuGet.org.

Checksums

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

New Errors inbox features

• User tracking: You can now see the number of users impacted by an error group. Identify the end user with the setUserId method.
• Error fingerprint: Are your error occurrences grouped poorly? Set your own error fingerprint via a callback function.

New Features

• Agent API now supports associating a User Id with the current transaction. See our ITransaction API documentation for more details. #1420
• Agent API now supports providing a callback to determine what error group an exception should be grouped under. See our SetErrorGroupCallback API documentation for more details. #1434
• Adds the Supportability/Logging/Forwarding/Dropped metric to track the number of log messages that were dropped due to capacity constraints. #1470

Fixes

• Reduce redundant collector request data payload logging in the agent log at DEBUG level. #1449
• Fixes #1459, a regression in NLog local decoration when logging messages with object parameters. #1480

Other

• Renamed NewRelic.Providers.Wrapper.Asp35 to NewRelic.Providers.Wrapper.AspNet since this wrapper instruments multiple versions of ASP.NET. Updated installers to remove old Asp35 artifacts. #1448

Once published, you can find the release artifacts for this release here or on NuGet.org.

Checksums

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

New Features

• When running on Linux, distro name and version will be reported as environment settings #1439

Fixes

• Fixes #1353 so that out-of-process .Net Core web applications are instrumented according to the <applicationPools> setting in the newrelic.config file. 1392
• Update NLog to improve local log decoration coverage. #1393

Once published, you can find the release artifacts for this release here or on NuGet.org.

Checksums

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

New Features

• Postgres client instrumentation support has been extended to include the following versions: 4.0.x, 4.1.x, 5.0.x, 6.0.x and 7.0.x. #1363
• Enables gzip compression by default for Infinite Tracing. #1383

Fixes

• Fix a race condition when using SetApplicationName. #1361
• Resolves #1374 related to enabling Context Data for some loggers. #1381
• Add missing supportability metrics to gRPC response streams and improve Infinite Tracing integration test reliability #1379

Deprecations

Infinite Tracing for .NET Framework applications will be deprecated in May 2023. The Infinite Tracing feature depends on the gRPC framework to send streaming data to New Relic. The gRPC library currently in use, gRPC Core, has been in the maintenance-only phase since May 2021, and will be deprecated as of May 2023.

The .NET Agent on .NET Core has been migrated to gRPC for .NET per the guidance from grpc.io. However, this library doesn't have the full functionality that is required for Infinite Tracing on .NET Framework applications. Those applications will continue to use gRPC Core until May 2023, at which time we'll end support for Infinite Tracing for .NET Framework. We may revisit this decision in the future if the situation changes. #1367

Other

• Resolved several static code analysis warnings relating to unused variables and outdated api usage. #1369
• Update gRPC log message when a response stream is automatically cancelled due to no messages in a time period. #1378
• Proxy configuration for Infinite Tracing should be specified using only the https_proxy environment variable. grpc_proxy is no longer supported for all application types.

Once published, the release artifacts for this release can be found here or on NuGet.org.

Checksums

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

Fixes

• StackExchange.Redis versions 2 and above use a new wrapper with improved performance and reduced network overhead. #1351

New Features

• Custom instrumentation now supports targeting specific assembly versions. See the documentation for more details. #1342
• RestSharp client instrumentation support has been extended to include the following versions: 106.11.x, 106.12.0, 106.13.0, and 106.15.0. #1352
• RestSharp client instrumentation has been verified for versions 107.x and 108.x. For newer versions of RestSharp, external segments/spans are actually generated via our instrumentation of HttpClient. #1356
• .NET TLS options are now logged during startup. #1357

Once published, the release artifacts for this release can be found here or on NuGet.org.

Checksums

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

Fixes

• Resolves #1346 where some NuGet packages were incomplete for the 10.5.0 release. Impacted packages have been delisted from NuGet. (#1347)

Once published, the release artifacts for this release can be found at https://download.newrelic.com/dot_net_agent/latest_release/ or on NuGet.org.

Checksums

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

Fixes

• Attribute collections in the agent will now more reliably track the number of attributes contained, and allow updates to attributes that already exist in the collection when collection limits have been reached (255 global attributes, 65 custom attributes). (#1335)
• The agent has been updated to use System.Net.Http.HTTPClient to send data to New Relic instead of System.Net.WebRequest, in order to fix issue #897, as well as remove use of a deprecated library. (#1325)

Once published, the release artifacts for this release can be found at https://download.newrelic.com/dot_net_agent/latest_release/ or on NuGet.org.

Checksums

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

New Features

• Support for .NET 7 has been verified with the GA version of the .NET 7 SDK. Please note that if you use dynamically-created assemblies, there is a bug in .NET 7 that prevents them from being instrumented at this time.
• Application log fowarding can now be configured to capture and forward context data to New Relic. Details (including how to enable and configure this new feature) can be found here.
• The NewRelic.Agent NuGet package now includes the Linux Arm64 profiler. This can be found in the newrelic/linux-arm64 directory. Configure your CORECLR_PROFILER_PATH environment variable to use this version of the profiler when deploying to linux ARM64 targets.
• When finest logs are enabled, the transaction guid will be applied to attribute limit log messages, if present.

Fixes

• Resolves potential crash when using Infinite Tracing. #1319

Once published, the release artifacts for this release can be found at https://download.newrelic.com/dot_net_agent/latest_release/ or on NuGet.org.

Checksums

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.

New features

• Custom event limit increase
  • This version increases the default limit of custom events from 10,000 events per minute to 30,000 events per minute. In the scenario that custom events were being limited, this change will allow more custom events to be sent to New Relic. There is also a new configurable maximum limit of 100,000 events per minute. To change the limits, see the docs for max_samples_stored. To learn more about the change and how to determine if custom events are being dropped, see our Explorers Hub post. #1284

Checksums

Updating

• Follow standard procedures to update the .NET agent.
• If you're using a particularly old agent, review the list of major changes and procedures for updating legacy .NET agents.