Important: Upcoming Changes To Capabilities Across Synthetics; APM; Java, PHP, Infrastructure, & Mobile Agents; Health Maps; StatsD; and Legacy dashboards

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

Support ending upon release of next version:

  • Java Agent: Ending support for Java 7

Support ending May 2021:

  • Synthetics: Label API
  • PHP Agent: Ending support for ZTS builds
  • Mobile agent TLSv1.0 & TLSv1.1 ingress
  • Health Maps

Support ending June 2021:

  • Synthetics: Private minion watchdog report
  • Infra-agent: Ending support for Operating systems beyond manufacturer EOL
  • StatsD v1 on-host integration
  • Legacy custom dashboards

Support ending August 2021:

  • APM: Errors Classic UI

Read below for additional information about individual features.
–––

Java Agent: Ending support for Java 7

What is happening?

  • Starting with the release of our next major Java agent version (7.0.0), we will no longer support Java 7 in our new releases. This means that to use our agent from that version onward, you must be on Java 8 - or a higher supported version.
  • We encourage you to plan for upgrading your Java based environments (Java 8 or higher) to take advantage of the increased performance and stability benefits. As you do this, you will be prepared to also leverage the value added by newer versions of our Java agent.

Why?

  • Few of our customers (less than 1%) are still using Java 7, which has ended public updates since 2015. Continuing to support this older version in our agent codebase requires a significant amount of effort and prevents us from taking advantage of many of the Java enhancements added to the platform starting with the introduction of Java 8.
  • Some features – like our Realtime Profiling for Java – simply cannot be implemented using Java 7. Making this change allows us to simplify our code, making it easier for us to deliver more value to our customers.

When?

  • Upon the next major Java agent release, Java 7 support will be deprecated.

  • We understand that upgrading Java versions takes time and planning - don’t worry, your agent versions prior to 7.0.0 will continue to work and New Relic will continue to support you. However, you will lose the ability to take advantage of new agent releases.

Links to other resources

–––

Synthetics Label API

What is happening?

Why?

  • This endpoint is available as read-only and could be providing incorrect data. Switching to the tags endpoint will ensure you will receive more accurate data.
  • Synthetics will be adopting tags as we migrate to the New Relic One platform. Tags offer a versatile way to identify entities across the New Relic One platform. Many features leverage tags to automatically group entities showing the status of a group of entities (eg: Workloads can group APM, Browser, and Synthetics entities by tag).

When?

  • Support for the label API will end on May 26th, 2021.

Links to other resources

–––

PHP Agent: Ending support for ZTS builds

What is happening?

  • This will be the last release of the PHP Agent in which ZTS builds are supported. In the future, ZTS builds may not be provided, and support may be completely pulled from the codebase.

Why?

  • Very few, if any, of our customers use ZTS builds. Reducing the number of PHP agent builds will make it easier for us to deliver more value to our customers.

When?

  • May 31st, 2021 (approximate date of next release)

Links to other resources

–––

Mobile Agent TLSv1.0 & TLSv1.1 ingress

What is happening?

  • We will no longer allow Mobile Agents to send data to New Relic with a TLSv1.0 or v1.1 handshake.
  • TLSv1.2 is fully supported since Android 5.0, but Mobile Agent traffic from < Android 5.0 will not function.

Why?

  • TLS deprecation is important to protect the security of your data, to satisfy our customers’ expectations of security, and to comply with standards bodies such as FedRAMP.
  • TLS 1.0 (and to a lesser extent, 1.1) does not include many of the protections instituted in later versions of TLS. Simply put: it’s easier to hack TLS 1.0 than it is to hack TLS 1.2. Additionally, cryptographers believe that there may be possible downgrade attacks, which would allow an attacker to force a client to this weaker version if it is supported server-side. Only by removing support for the older versions on the server-side can we guarantee our customers use the stronger versions.

When?

  • May 2021

–––

Health Maps

What is happening?

Why?

  • We designed New Relic Navigator with more comprehensive capabilities than Health Maps.
  • New Relic Navigator lets you explore all your entities belonging to all your accounts, focusing on specific entity types or specific groups of entities organized by tags to quickly zero in on issues. When you have thousands, or tens of thousands of hosts, containers, and services, this capability makes it easy for you to explore everything in one place.

When?

  • May 26th, 2021

–––

Synthetics: Private minion watchdog report

What is happening?

  • The private minion watchdog report will be deprecated and replaced by NRQL alerts.
  • Synthetics originally created an email that was used to alert account administrators when their private locations were having issues; this was called the private minion watchdog report. Since then we have replaced these reports with NRQL alerts.

Why is this change being implemented?

  • Few customers are using the private minion watchdog report, and NRQL alerts provide a more reliable and flexible solution.

When?

  • June 2021

Links to other resources

–––

Infra-agent: Ending support for Operating systems beyond manufacturer EOL

What is happening

  • The New Relic Infrastructure agent will be no longer available for the following operating systems:
    • CentOS 5/Red Hat 5
  • The New Relic Infrastructure agent will no longer support for the following operating systems:
    • CentOS 6/Red Hat 6
    • Amazon Linux 1
    • Debian 8
    • Ubuntu 14
    • SLES 11.x/11.4

Why?

  • The operating systems listed above have been EOL’d by their manufacturers between April 2019 and Dec 2020.
  • New Relic does not support operating systems beyond the manufacturer end-of-life.

What does my customer need to do?

  • Upgrade to newer versions of their OS

When?

  • For no longer available OSs:
  • For no longer supported OSs:
    • June 1st, 2021

Links to other resources

–––

StatsD v1 on-host integration

What is happening?

  • As of June 1st, support for StatsD monitoring integration version 1 will be discontinued. Migrate to the second version for an improved experience.

Why?

  • The second version of our StatsD monitoring integration has a new and improved architecture. Improvements include: simpler configuration, and a simpler method for adding tags (key-value pairs).

When?

  • June 1st, 2021

Links to other resources

–––

Legacy custom dashboards

What is happening?

Why?

When?

  • June 16th, 2021

Links to other resources

3 Likes