.NET agent release notesRSS

새로운 기능

• 이제 모니터링 애플리케이션을 다시 시작하지 않고도 커스텀 측정 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.

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:

• Windows
• Linux
• Docker
• Azure App Services

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

• 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

• 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

• Follow standard procedures to upgrade 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 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

• Follow standard procedures to upgrade 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

• 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

• Follow standard procedures to upgrade 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 instrumentation for OWIN hosted Web API applications on .NET framework using Microsoft.Owin.Host.HttpListener versions 3.* Instrumentation includes async-await support.
• Adds async-await support for OWIN hosted Web API applications on .NET framework using Microsoft.Owin.Host.HttpListener versions 2.*.

Fixes

• Fixed an issue where SQL instrumentation could raise exceptions and cause it to shutdown.
• Error traces now include the full stack trace, including any inner exceptions.

Upgrading

• Follow standard procedures to upgrade 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

• Performance improvements when slowSQL is enabled, particularly for apps with lots of slow SQL queries.

Fixes

• Fixed an issue that was preventing the proper setting of Key Transaction Apdex scores based on their configured ApdexT values.
• Fixed an issue preventing the collection of transaction traces for Key Transactions based on their configured ApdexT values.

Upgrading

• Follow standard procedures to upgrade 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

• Agent overhead is reduced for transactions composed of an unusually large number of small activities.

Fixes

• Enhanced low-level logging to improve supportability.
• Fixed a problem with new installs using the Thin Installer where false permission errors could be reported.

Upgrading

• Follow standard procedures to upgrade 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.