Important: Upcoming Changes to Support and Capabilities Across Browser; Node.js agent; Query builder; .NET agent; APM errors; & Distributed tracing

New Relic will discontinue support for a variety of capabilities across the platform. These include:

Support ending July 2021:

  • Node.js 10
  • Distributed tracing analytics prototype

Support ending August 2021:

  • Browser: AMP page monitoring private beta

Support ending September 2021:

  • Query builder basic mode (Moved to Q3)
  • .NET agent support for deprecated APIs

Support ending November 2021 (UPDATED):

  • APM Errors Classic UI

Read below for additional information about individual features.

–––

Node 10 support

What is happening?

  • We will no longer support Node 10 in new versions of the New Relic Node.js agent for versions 8.0.0 and higher. OpenJS Foundation’s maintenance cycle for Node.js 10 has ended, meaning there are no longer updates, bug fixes or security patches for Node 10.
  • We encourage customers to upgrade to supported versions of Node and the latest version of the Node.js agent to take advantage of the newest Node.js agent features.
  • However, if you want to continue using Node 10, you can do so by staying on a version below v8.0.0 of the New Relic Node.js agent.

Why?

  • Every year Node.js comes out with a new even numbered release. The maintenance cycle for Node.js 10 ended in April 2021. This means since April 2021, Node.js 10 has not received updates, bug fixes or security patches. Also to note, the newest version of Node.js, Node.js 16, was released at the same time, and we provide support for Node.js 16.
  • Because Node.js 10 no longer receives updates, bug fixes or security patches, upgrading from Node.js 10 will ensure your applications built with Node.js 10 aren’t susceptible to bugs or vulnerabilities. By moving off of Node.js. 10 and upgrading to the latest version of the New Relic Node.js agent, you will be able to take advantage of the new agent features.

When?

  • July 31, 2021

Links to other resources

–––

Distributed Tracing analytics Nerdlet

What is happening?

  • New Relic originally released a prototype for distributed tracing as a nerdlet application. Since then, we have launched a new Distributed Tracing user experience in New Relic One that already includes all the features in the prototype.
  • We will be removing the distributed tracing analytics nerdlet from the New Relic One app catalog.
  • Users should use the Tracing user interface in New Relic One for distributed tracing.

Why?

  • Using the new integrated tracing interface in New Relic One means ease of access and a more unified experience on the platform. You will not lose any functionality previously available in the DT analytics prototype.

When?

  • July 31, 2021

Links to other resources

–––

Browser: AMP page monitoring private beta

What is happening?

  • Over four years ago, we delivered a private beta browser agent for collecting performance data from HTML pages formatted for Google’s Accelerated Mobile Pages (AMP) project.
  • This private beta is now closed. This feature and all related services will be deprecated in August 2021.

Why?

  • As a private beta feature, we have received little feedback and bug or enhancement requests. Adoption has also been relatively low, so New Relic discontinuing this feature will allow us to better provide support for other features.

When?

  • As of August 1, this feature and all related services will be deprecated

Links to other resources

–––

Query builder basic mode (Moved to Q3 tentatively)

What is happening?

  • The New Relic One query builder currently has three modes to fetch, analyze, and visualize your data: NRQL, PromQL-style, and Basic.
  • The basic mode will be removed in favour of unifying the basic experience in the data explorer.
  • For guided data visualization, users can use the data explorer; and for more advanced users, they can continue to use NRQL queries in the query builder.

Why?

  • The purpose of the query builder’s basic mode is to help users to explore data with basic knowledge of the platform, without needing to write NRQL queries. However, the data explorer fulfils the same purpose in a more user-friendly and intuitive way. Users can explore events and metrics on the data explorer UI, or select the Logs and Traces query interfaces to explore those.

When?

  • September 1, 2021 (Moved to Q3 tentatively)

Links to other resources

–––

.NET agent support for deprecated APIs

What is happening?

  • During the next major release of the New Relic .NET agent, a small subset of APIs, configuration options, and installation options will be replaced by new methods. The deprecated APIs and methods will be removed and no longer supported by the New Relic.
  • Anything being removed has a modernized replacement. This will only affect customers upgrading to a .NET agent v9.x release and using a deprecated item.
  • For explicit guidance on how to know if your .NET applications are impacted and details on each change’s upgrade path, please refer to the migration documentation that will be published in August.

Why?

  • The .NET agent v9.0.0 release includes the necessary work to modernize the agent In this release, we will remove deprecated APIs that were marked deprecated.
  • No functionality will be affected.

When?

  • September, 2021

Links to other resources

–––

APM Errors Classic

What is happening?

  • The classic APM Errors UI (“Errors (classic)” in the navigation) will be discontinued in favor of the New Relic One APM Errors UI.

Why?

  • Currently there are multiple user interfaces to explore errors in your APM services/applications. In order to reduce confusion about where to get the most accurate source of truth for errors, the classic errors UI will be discontinued. By using the Errors UI, you will also get access to additional features and a faster experience.

When?

  • November 1, 2021

Links to other resources

  • New Relic One Errors documentation
  • See also the new Errors Inbox, a single place to proactively detect, prioritize, and take action on all your errors before they impact customers
1 Like