• EnglishEspañol日本語한국어Português
  • ログイン今すぐ開始

.NET agent release notesRSS

March 7, 2018
.NET agent v6.22.0.0

Fixes

  • Security Bulletin NR18-07: The agent will no longer run explain plans on MySQL queries which have multiple statements.

Upgrading

.NET agent v8.0.0.0

New Features

  • Adds stripExceptionMessages configuration option to the newrelic.config file. When enabled, this will remove error messages from errors that are reported to New Relic. This is the same behavior as having High-security mode enabled but can be used without High-security mode. The default value for this setting is false.

Fixes

  • Security Bulletin NR18-07: The agent will no longer run explain plans on MySQL queries that have multiple statements.

Other Changes

  • In order to increase security, disabling agent HTTPS communication via the service SSL configuration is no longer allowed.
  • WCF service parameters are now captured as request.parameters.* attributes and are no longer sent as service.request.* attributes.
  • Minimum version required for use in EU Datacenter.

Upgrading

February 20, 2018
.NET agent v7.1.229.0

New Features

  • Improved metadata collection for cloud providers. The agent now collects additional metadata when running in AWS, GCP, and Azure. This information is used to provide an enhanced experience when the agent is deployed on those platforms.

Fixes

  • Fixed an issue where transactions could be dropped when they included datastore segments and the following exception was logged: NewRelic ERROR: An exception occurred while doing some background work: System.NullReferenceException: Object reference not set to an instance of an object.
  • Fixed an issue where SOAP instrumentation would report System.Reflection.TargetInvocationException errors when a more specific error existed. Inner exceptions will now be reported when they exist.

Deprecation Warnings

The follow items are considered deprecated and will be removed with the upcoming 8.x major release:

  • Disabling agent HTTPS communication via the service SSL configuration will no longer be allowed starting in 8.x versions of the agent.
  • WCF service parameters will no longer be sent as service.request.* attributes starting in 8.x versions of the agent. These parameters will be sent in the form request.parameters.*.

Upgrading

February 8, 2018
.NET agent v6.21.0.0

Fixes

  • Security Bulletin NR18-04: Fixes issue where error messages were not fully being filtered out of error traces and error events when High-security mode was enabled.

Upgrading

January 22, 2018
.NET agent v7.0.2.0

New Features

  • Modifying custom instrumentation XML files can now be performed without having to restart the monitored application. Instrumentation updates will be applied ‘dynamically’ at runtime. This feature required functionality provided by new APIs introduced in .NET Framework 4.5 and newer, which this release also addresses (see ‘Framework Support’ section below).

Fixes

  • Security Bulletin NR18-04: Fixes issue where error messages were not fully being filtered out of error traces and error events when High-security mode was enabled.
  • Fixed an issue with automatic browser monitoring which could cause a stack overflow exception.
  • For custom instrumentation, the metricName parameter will be honored without needing to set transactionNamingPriority.
  • The scriptable installer will now successfully install and uninstall in scenarios where there is a space in the path to the installation files.

Framework Support

Upgrading

December 18, 2017
.NET agent v6.20.166.0

New Features

  • The request URI for a web transaction will now be included as an attribute of transaction events and error events.
  • The New Relic .NET Status Monitor has been retired and is no longer included in the install. The replacement tool is New Relic Diagnostics. To download the most recent version, select the link in the New Relic Diagnostics documentation.

Fixes

  • Security Bulletin NR17-06: Fixes issue where query parameters were being included in the URL property of transaction trace segments for external calls (uses of System.Net.HttpClient, System.Net.WebRequest, or third-party libraries which are built on top of those). Query parameters will no longer be included in transaction trace segments.
  • Transaction names will be rolled up for web transactions resulting in a 400 or 500 level HTTP status code and a higher priority name has not been set. This helps prevent metric grouping issues.
  • Fixed error that could result in the one time loss of a metric and/or transaction for an instrumentation point at the start of monitoring an application. "...NewRelic ERROR: Tracer invocation error: System.ArgumentException: An item with the same key has already been added. Key: ..."
  • Minor log level adjustments in the profiler logging. Suppresses benign error Failed to tokenize method signature: class System.Reflection.Assembly System.CannotUnloadAppDomainException::LoadAssemblyOrThrow(string)
  • [.NET Core 2.0] For .NET Core agent users on Linux, this release fixes a problem with the run.sh convenience script in combination with a custom installation path.
  • [.NET Framework] Fixes issue resulting in SerializationExceptions when using .Net Remoting.

Upgrading

November 30, 2017
.NET agent v6.19.330.0

New Relic Agent for .NET Core 2.0 GA

Highlights

  • Windows and Linux support, including Azure App Services and Docker
  • Automatic instrumentation for ASP.NET Core applications running on Kestrel
  • External calls via HttpClient
  • Database instrumentation for System.Data.SqlClient, Npgsql, and MySql.Data
  • Custom instrumentation via XML and transaction/trace attributes
  • NewRelic.Agent.Api support

For a more detailed list, see the compatibility documentation.

The .NET Core 2.0 agent is a separate install and can live side-by-side on the same server as the .NET Framework agent. For installation information, follow the procedures for your operating system as applicable:

New Shared Features

  • Database instrumentation performance has been improved.
  • Explain plans are no longer captured by default for supported database systems: Microsoft SQL Server and MySQL. Explain plans can be enabled via configuration.

Updating the Agent

November 2, 2017
.NET agent v6.18.139.0

New Features

  • The agent now supports running in FIPS compliance mode.

Fixes

  • Fixed an issue that caused some transactions to report start time in the server's local time zone instead of UTC.
  • Additional bug fixes to remedy a SerializationException caused by the agent.

Upgrading

October 3, 2017
.NET agent v6.17.387.0

New Features

  • Adds support for RestSharp library. The Agent can now instrument async and non-async methods from a RestSharp client. For supported methods, please visit here.
  • The application name reported to New Relic APM can now be set by defining the NEW_RELIC_APP_NAME environment variable.

Fixes

  • Fixed some situations where SerializationException occurs in the agent log file.
  • The injection of Browser Monitor JavaScript directly above the body tag on a page should occur less often.
  • Fixes issue where datastore instance information would not be reported for some NpgsqlCommand async calls.
  • Fixed remaining cases where 9-digit SQL trace identifiers were generated, failing Data Loss Prevention monitors which interpret the value as a Social Security Number.

Upgrading

August 28, 2017
.NET agent v6.16.178.0

New Features

  • Custom instrumentation can now be declared by applying the agent API's new Transaction and Trace attributes to methods. Using the Transaction attribute, transactions can be marked as Web vs. Non-Web. For more information, see Custom instrumentation via attributes.

Fixes

  • Fixes bug preventing instrumented apps from shutting down due to Profiler failure to detach.

Upgrading

Copyright © 2024 New Relic株式会社。

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.