.NET agent release notesRSS

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.

Fixes

• In some cases, the trace breakdown table overreported segment times. This happened when these three conditions were met, 1. instrumentation occurred through custom XML files, 2. the segment name was overridden, and 3. the segment contained child segments.

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.

Fixes

• Fixed an issue preventing injection of a mscorlib reference into every module.

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.