.NET agent release notesRSS

New Features

• [.NET Framework] The .NET Framework agent now supports instrumenting ASP.NET Core applications that are running on .NET Framework. The .NET Core specific agent is still required for instrumenting applications running on .NET Core.

Fixes

• Fixed issue where deadlocks could occur in some situations when a ThreadAbortException was thrown within a client application.
• Fixed issue where only the first transaction name set via API call to SetTransactionName() would be honored. Now, the last call to SetTransactionName() will be the name applied to the transaction.
• [.NET Core 2.0] Fixed issue with the .NET Core agent on Windows where the CORECLR_PROFILER_PATH environment variable was not being expanded properly in certain deployment scenarios.
• [.NET Framework] Fixed issue introduced in agent version 8.1.709.0 that caused some .NET Framework applications to throw the following exception: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.

Upgrading

• Follow standard procedures to update the .NET agent.
• If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents.

New Features

• [.NET Framework] The .NET Framework agent now supports instrumenting ASP.NET Core applications that are running on .NET Framework. The .NET Core specific agent is still required for instrumenting applications running on .NET Core.

Fixes

• Fixed issue where deadlocks could occur in some situations when a ThreadAbortException was thrown within a client application.
• Fixed issue where only the first transaction name set via API call to SetTransactionName() would be honored. Now, the last call to SetTransactionName() will be the name applied to the transaction.
• [.NET Core 2.0] Fixed issue with the .NET Core agent on Windows where the CORECLR_PROFILER_PATH environment variable was not being expanded properly in certain deployment scenarios.

Upgrading

• Follow standard procedures to update the .NET agent.
• If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents.

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

• Follow standard procedures to update the .NET agent.
• If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents.

Fixes

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

Upgrading

• Follow standard procedures to update the .NET agent.
• If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents.

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

• Follow standard procedures to update the .NET agent.
• If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents.

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

• Follow standard procedures to update the .NET agent.
• If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents.

새로운 기능

• 이제 모니터링 애플리케이션을 다시 시작하지 않고도 커스텀 측정 XML 파일을 수정할 수 있습니다. 측정 업데이트는 런타임에 ‘동적으로’ 적용됩니다. 이 기능은 .NET 프레임워크 4.5 이상에 도입된 새로운 API에서 제공하는 기능을 필요로 하며, 이번 릴리스에서도 이를 다룹니다(아래 ‘프레임워크 지원’ 섹션 참조).

수정 사항

• 보안 게시판 NR18-04: 고보안 모드가 활성화되었을 때 오류 트레이스 및 오류 이벤트에서 오류 메시지가 완전히 필터링되지 않던 문제를 수정했습니다.
• 자동 브라우저 모니터링에서 스택 오버플로 예외를 유발할 수 있는 문제를 수정했습니다.
• 커스텀 측정의 경우 transactionNamingPriority를 설정할 필요 없이 metricName 파라미터가 적용됩니다.
• 이제 설치 파일 경로에 공백이 있는 시나리오에서도 스크립트 가능한 인스톨러가 성공적으로 설치 및 제거됩니다.

프레임워크 지원

• 이번 에이전트 릴리스에서는 4.5 이전 버전의 .NET 프레임워크에 대한 지원을 제거합니다. 자세한 내용은 작년 11월에 작성된 관련 커뮤니티 게시물을 확인해 주십시오.
• 이것은 6.x 에이전트(이전 .NET 프레임워크를 지원하는)의 수명 종료가 아니며, 계속해서 작동하고 뉴렐릭에 보고합니다.

업그레이드

• .NET 에이전트를 업데이트 하려면 표준 절차를 따르세요.
• 특히 오래된 에이전트에서 업그레이드하는 경우, 주요 변경 사항 목록과 구형 .NET 에이전트 업그레이드 절차를 검토하십시오.

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

• Follow standard procedures to update the .NET agent.
• If you are upgrading from a particularly old agent, review the list of major changes and procedures to upgrade legacy .NET agents.