.NET agent release notesRSS

Security

• Update Grpc.Net.Client library to address Dependabot alerts. (#1768) (#1769) (eee7564)

New Features

• Add support for filtering log events based on a list of log levels so that they are not forwarded to New Relic. Also adds new logging metrics to count the total number of filtered log events (Logging/denied). Refer to our application logging configuration documentation for more details. (#1760) (#1761) (#1762) (#1766) (aadce3a)
• Instrument OpenAsync() for SQL libraries. (#1725) (a695ce6)

Fixes

• Refactor StackExchange.Redis v2+ instrumentation to eliminate potential memory leaks. (902b025)
• Remove invalid trailing comma added to W3C tracestate header. (#1779) (790a3b7)
• Update the MSI UI to clean up formatting and readability issues. (#1748) (3fbc543)

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.

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date. See the New Relic .NET agent EOL policy doc for information about agent releases and support dates.

Fixes

• Resolved an issue in the all_solutions.yml workflow where the MSI installers were built with a self-signed certificate rather than the production code signing certificate. (386a277)

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.

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date. See the New Relic .NET agent EOL policy doc for information about agent releases and support dates.

New Features

• Add instrumentation for newer MongoDB.Client methods. (#1732) (1aa5680)
• Add support for MySql.Data version 8.0.33+. (#1708) (69d15df)

Fixes

• Add more validation to msi installer. (#1716) (d7bb7f2)
• Cache the AgentEnabled setting value. (#1723) (1624938)
• Exclude WebResource.axd and ScriptResource.axd from browser instrumentation (via default config). (#1711) (2fcce95)
• Format and log audit-level messages only when audit logging is enabled. (#1734) (f71521f)
• Handle empty Request.Path values in AspNetCore middleware wrapper. (#1704) (8b734a5)
• Include config file path in the "Agent is disabled " message on all platforms. (#1727) (1a56612)
• Update install script to correctly stop and restart IIS. (#1740) (3b91dff)

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.

We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping your agent up to date. See the New Relic .NET agent EOL policy doc for information about agent releases and support dates.

We recommend you update the agent regularly, at least every 3 months. Read more about keeping your agent up to date.

This release is supported for one year after its release date. For a full list of supported versions and their support periods, please see our EOL policy doc.

New Features

• Add detailed assembly reporting to enable Vulnerability Management support. (#1685) (f249753)
• Adds minimal support for Devart Oracle client. (181a628)
• Use Serilog instead of log4net for internal logging. (#1661) (51080df)

Fixes

• Clearing transaction context for held transactions and async WCF client instrumentation timing. (#1608) (db9a48e)
• Stop double injecting headers with HttpClient on .NET Framework (#1679) (e8bdc34)

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.

We recommends you to update the agent regularly, at least every 3 months. Read more about keeping your agent up to date.

This release is supported for one year after its release date. For a full list of supported versions and their support periods, please see our EOL policy doc.

As of this release, the oldest supported version is .NET agent 8.27.139.0.

New Features

• Add additional logging when RUM injection is being skipped. (#1561) (e1b8eca)
• Add instrumentation for .NET Elasticsearch clients. (#1575) (8e49d7b)
• Move TLS config logging closer to connect. (#1562) (0ff3ddd)

Fixes

• Add missing instrumentation to MSI installer (#1569) (b65b117)
• Add NServiceBus instrumentation to the MSI installer for .NET Core/5+. (#1576) (3cae03e)
• IsOsPlatform() can fail on older .NET Framework Versions (#1552) (699c205)

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.

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.