New Relic EOL

Deprecation notice: Kubernetes

Thu, 16 Dec 2021 00:00:00 +0000

Effective Monday, 1 January 2022, our Kubernetes integration drops support for Kubernetes v1.15 and lower. The Kubernetes integration v2.8.0 and higher will only be compatible with Kubernetes versions 1.16 and higher. For more information, read this note or contact your account team.

Background

Enabling compatibility with the latest Kubernetes versions and adding new features to our Kubernetes offering prevents us from offering first-class support to versions prior to v1.16.

What is happening?

The latest Kubernetes version v1.22 has API incompatibilities with versions prior to v1.16.
Most major Kubernetes cloud providers have already deprecated v1.15 and lower.

What do you need to do?

It's easy: Upgrade your Kubernetes clusters to a supported version.

What happens if you don't make any changes to your account?

The Kubernetes integration may continue to work with end-of-lifed versions. However, we can't guarantee the quality of the solution as new releases may cause some incompatibilities.

Note that support requests regarding these end-of-lifed versions won't be accepted.

Deprecation notice: Kubernetes

Fri, 15 May 2020 00:00:00 +0000

Effective Wednesday, 12 August 2020, Kubernetes integration v1.7 or lower will be deprecated. To avoid losing data, upgrade to the latest version. For more information, read this note or contact your account team.

Background

In order to provide the best possible experience for monitoring Kubernetes, we are merging the Kubernetes cluster explorer into New Relic, where you'll enjoy all the latest features.

What is happening?

We will support Kubernetes integrations v1.7 or lower until Wednesday, 12 August 2020.

Starting on July 1st the Kubernetes cluster explorer will only be available at one.newrelic.com > All capabilities > Kubernetes Cluster Explorer. The Kubernetes cluster explorer will only be compatible with Kubernetes integrations v.1.8 and newer from Wednesday, August 12th.

Therefore in order to enjoy the latest features and to be fully compatible with the New Relic Kubernetes cluster explorer, you must upgrade your Kubernetes integration to the latest version.

What do you need to do?

Follow the instructions here to upgrade to the latest version of the Kubernetes integration.

What happens if you don't make any changes to your account?

The Kubernetes integration will still send data to the New Relic platform, though the Kubernetes cluster explorer will not work for clusters running Kubernetes integration versions v1.7 or older after Wednesday, 12 August. In other words, the integration will still send data, however you will be unable to view that data in the cluster explorer.

End of life for the browser monitoring `createTracer()` API call

Wed, 24 Apr 2024 00:00:00 +0000

On October 15, 2024, New Relic will end of life the browser monitoring createTracer() API call.

New Relic is updating the browser SPA agent to be more performant, with improved accuracy and fewer lines of code. These updates simplify the agent, letting customers diagnose issues with their browser apps more easily. Before New Relic can update the browser SPA agent, we need to remove the createTracer() API.

Accounts using the createTracer() API at the time of end of life will lose performance metrics about their SPAs.

What you need to do

We recommend that you migrate to the addPageAction() API call to collect time data about sub-components on your pages.

See our doc on addPageAction for information on how to implement this API call.

End of life for CPM and legacy synthetic monitoring runtimes

Mon, 22 Apr 2024 00:00:00 +0000

On October 22, 2024, New Relic will end of life (EOL):

The Containerized Private Minion (CPM) capability
Legacy synthetic monitoring runtimes, including our legacy Chrome 72 (or older) and Node version 10 (or older) runtimes

What you need to do

Update to the latest runtimes by following procedures in our transition guide, or by contacting support.

The new runtimes improve on our legacy runtime environment, including but not limited to these changes:

Updating to the new runtime will remove certain CVE findings that cannot be resolved due to the legacy runtime design and backward compatibility requirements of the Containerized Private Minion (CPM)
Support for newer Chrome and Node.js versions, including easier upgrade paths
More frequent browser version updates
Access device emulation and other new capabilities

All customers must be on the new runtime by October 22, 2024 in order to prevent degradation.

Read on to learn more about how the update affects your public or private locations.

For public locations

New Relic will update all broken link and certificate check monitors to the new runtime.
Customers should update their scripted API, scripted browser, and step monitors to the new runtime using the runtime upgrade UI before October 22, 2024.
- If you do not update, we’ll force update your monitors to the new runtime on the end-of-life date. This may result in check failures and triggered alerts.
- Before updating to the new runtime, use the test results from the runtime upgrade UI to determine which monitors need to be modified.
As of August 26, 2024, customers will be unable to create new monitors using legacy runtimes on public locations.

For private locations

You should update to our new job manager, which provides support for our new runtime on private locations. If you don't, your monitors will stop running at the end-of-life date.
Once you're using the new job manager, update your monitors to the new runtime using the runtime upgrade UI. This includes all non-ping monitor types.
- If you do not update, we'll force update your monitors to the new runtime. This may result in check failures and triggered alerts.
- Remember to use the test results from the runtime upgrade UI to determine the monitors that may require modifications before updating to the new runtime.
On April 5, 2024, we added support for advanced features of the Containerized Private Minion (CPM) to the Synthetics Job Manager:
- Verified script execution (VSE)
- Custom environment variables
- Custom node modules
Customers will be unable to create new monitors using legacy runtimes on private locations as of August 26, 2024.

Links to additional resources

Deprecation notice: Kubernetes

Fri, 15 Sep 2023 00:00:00 +0000

Effective Friday, 15 September 2023, our Kubernetes integration drops support for Kubernetes v1.22 and lower. The Kubernetes integration v3.17.0 and higher will only be compatible with Kubernetes versions 1.23 and higher. For more information, read this note or contact your account team.

Background

Enabling compatibility with the latest Kubernetes versions and adding new features to our Kubernetes offering prevents us from offering first-class support to versions v1.22 and lower.

What is happening?

The latest Kubernetes version v1.27 has API incompatibilities with versions v1.22 and lower.
Most major Kubernetes cloud providers have already deprecated v1.22 and lower.

What do you need to do?

It's easy: Upgrade your Kubernetes clusters to a supported version.

What happens if you don't make any changes to your account?

The Kubernetes integration may continue to work with end-of-lifed versions. However, we can't guarantee the quality of the solution as new releases may cause some incompatibilities.

Note that support requests regarding these end-of-lifed versions won't be accepted.

Deprecation notice: Kubernetes

Wed, 03 Jul 2024 00:00:00 +0000

Effective Wednesday, July 3, 2024, our Kubernetes integration drops support for Kubernetes v1.25 and lower. The Kubernetes integration v3.29.0 and higher will only be compatible with Kubernetes versions 1.26 and higher. For more information, read this note or contact your account team.

Background

Enabling compatibility with the latest Kubernetes versions and adding new features to our Kubernetes offering prevents us from offering first-class support to versions v1.25 and lower.

What's happening

Most major Kubernetes cloud providers have already deprecated v1.25 and lower.

What do you need to do

It's easy: Upgrade your Kubernetes clusters to a supported version.

What happens if you don't make any changes to your account

The Kubernetes integration may continue to work with unsupported versions. However, we can't guarantee the quality of the solution as new releases may cause some incompatibilities.

Please note that we won't accept support requests for these versions that have reached the end of life stage.

End of life for Google Core Web Vital FID metric

Thu, 01 Aug 2024 00:00:00 +0000

On September 9, 2024, Google is deprecating the FID metric, in favor of Interaction to Next Paint (“INP”). Since New Relic uses certain libraries and APIs that leverage the FID metric, you will need to take the actions below before September 9, 2024 to avoid inaccurate or unexpected behavior with custom dashboards, alerts, and service level reporting.

What you need to do

To avoid inaccurate alerts, charts, and service levels, you must make the following changes before September 9, 2024:

Edit all custom dashboards using FID from the PageViewTiming event and replace with INP.
Edit any NRQL alert conditions using FID from the PageViewTiming event and replace with INP.
Edit any Service Levels using FID from the PageViewTiming event and replace with INP.

See the resources below for more information on how to identify which dashboards, alerts, and service levels use the FID metric.

Additionally, if you're using copy/paste browser instrumentation or are pinned to a version prior to version 1227, you must update the browser agent to version 1227 or higher to ensure that you have access to using the INP metric. To check which browser agent version you're on and for instructions on how to update your agent, please see our documentation. If you're using version 1227 or higher, you do not need to update your browser agent for this EOL; however, we recommend that customers keep all agents up to date.

Additional resources

Customers can use the following queries (either NRQL or via NerdGraph) to identify custom dashboards, alerts, and service levels that use the FID metric.

Custom dashboards

Use the NrdbQuery event query to find whether FID is being used in a custom dashboard.

SELECT uniques(source.dashboardId) FROM NrdbQuery WHERE query like '%firstInputDelay%' SINCE THIS WEEK

Alerts

Use the following alerts-specific NerdGraph query in your account to find whether FID is being used in a NRQL alert condition.

{
  actor {
    account(id: {account-id}) {
      alerts {
        nrqlConditionsSearch(searchCriteria: {queryLike: "firstInputDelay"}) {
          nextCursor
          nrqlConditions {
            id
            name
            nrql {
              query
            }
          }
        }
      }
    }
  }
}

Service Levels

Use the following browser monitoring and Service Levels-specific NerdGraph queries in your account to determine which SLIs are affected:

Get the GUID of all the browser monitoring apps that have SLIs:

{
  actor {
    entitySearch(
      query: "domain = 'BROWSER' AND type = 'APPLICATION' AND `tags.nr.has_slis` = 'true'"
    ) {
      results {
        entities {
          guid
        }
      }
    }
  }
}

For each of these browser monitoring apps, get the list of SLIs and check if in the WHERE clause of the query there is a reference to firstInputDelay:

{
  actor {
    entity(guid: "<browser_guid>") {
      serviceLevel {
        indicators {
          events {
            validEvents {
              where
            }
          }
        }
      }
    }
  }
}

Change to user and license keys

Thu, 01 Aug 2024 00:00:00 +0000

Beginning September 25, 2024, we're removing the ability to copy API keys from the UI. We're removing the Copy key option in the UI drop-down. This applies to user and license keys, both new and existing. If you have an automation that's dependent on scraping keys from the UI, please integrate using the NerdGraph API.

You're still able to retrieve your new and existing API keys through our NerdGraph API.

What you need to do

Before September 25, 2024: You need to store your existing API keys (both user and license keys) in a secure location outside New Relic, if you haven't done that. If you do not take this step, you will lose access to existing API keys in our UI.

After September 25, 2024: when generating new API keys (both user and license keys), you need to copy the key to a secure location outside New Relic before leaving the page.

For more information, see our docs.

Deprecation notice: Kubernetes

Wed, 15 Nov 2023 00:00:00 +0000

Effective Wednesday, November 15, 2023, our Kubernetes integration drops support for Kubernetes v1.23 and lower. The Kubernetes integration v3.20.0 and higher will only be compatible with Kubernetes versions 1.24 and higher. For more information, read this note or contact your account team.

Background

Enabling compatibility with the latest Kubernetes versions and adding new features to our Kubernetes offering prevents us from offering first-class support to versions v1.23 and lower.

What's happening

Most major Kubernetes cloud providers have already deprecated v1.23 and lower.

What do you need to do

It's easy: Upgrade your Kubernetes clusters to a supported version.

What happens if you don't make any changes to your account

The Kubernetes integration may continue to work with end-of-lifed versions. However, we can't guarantee the quality of the solution as new releases may cause some incompatibilities.

Please note that we won't accept support requests for these versions that have reached the end of their life.

Deprecation notice: Kubernetes

Tue, 29 Oct 2024 00:00:00 +0000

Effective Tuesday, October 29, 2024, our Kubernetes integration drops support for Kubernetes v1.26 and lower. The Kubernetes integration v3.30.0 and higher will only be compatible with Kubernetes versions 1.27 and higher. For more information, read this note or contact your account team.

Background

Enabling compatibility with the latest Kubernetes versions and adding new features to our Kubernetes offering prevents us from offering first-class support to versions v1.26 and lower.

What's happening

Most major Kubernetes cloud providers have already deprecated v1.26 and lower.

What do you need to do

It's easy: Upgrade your Kubernetes clusters to a supported version.

What happens if you don't make any changes to your account

The Kubernetes integration may continue to work with unsupported versions. However, we can't guarantee the quality of the solution as new releases may cause some incompatibilities.

Please note that we won't accept support requests for these versions that have reached the end of life stage.

Update to New Relic Synthetics IP ranges

Tue, 11 Feb 2025 00:00:00 +0000

In order to ensure the best service to our customers, New Relic will change the IP ranges for New Relic Synthetics checks effective May 14, 2025.

If Synthetics traffic is part of your allowlist, you will need to update your configurations to maintain monitor connectivity.

Failure to update your allowlist by May 14, 2025, may result in your synthetic checks failing to connect to your applications, potentially causing disruptions and alerts.

NOTE: If you do not allowlist by IP range, no action is required.

What's changing?

We will be migrating the IP address range for the New Relic service used by Synthetics public locations to align with our standard IP ranges used across other data ingest.

What action is required?

Before May 14, 2025, update your allow lists with the new IP ranges provided below.

New IP ranges to allowlist:
- 152.38.128.0/19
- 212.32.0.0/20
- 64.251.192.0/20
The following IP ranges will remain in use for the us-east-1 region:
- 44.202.178.0/24
- 44.202.180.0/23
- 44.210.68.0/24
- 44.210.110.0/25
After September 30, 2025, remove the old IP ranges from the allowlist. Failure to do so may result in failed connections and trigger alerts.

Old IP ranges to remove: The following table list the old IP ranges that you must remove before September 30, 2025.

Region Name	Region Location	Current CIDR Block Range
us-east-2	Columbus, OH, USA	3.145.224.0/24 3.145.225.0/25 3.145.234.0/24
us-west-1	San Francisco, CA, USA	3.101.204.0/23 3.101.212.0/24 3.101.209.192/26
us-west-2	Portland, OR, USA	35.89.46.0/23 35.92.27.0/24
ap-southeast-2	Sydney, AU	3.26.252.0/24 3.26.245.128/25 3.27.51.0/25
eu-central-1	Frankfurt, DE	3.71.170.0/24 3.71.103.96/27 3.75.4.128/25
eu-west-1	Dublin, IE	3.251.231.0/24 3.251.230.64/26 3.252.47.0/25
eu-west-2	London, England, UK	13.40.201.0/24 13.40.208.0/25 13.41.206.128/25 13.41.206.64/26

Additional Support

We understand that these changes may require some adjustments to your routine. Please know that we’re committed to supporting you throughout this process. If you have any questions or need further assistance, please don't hesitate to reach out to our support team.

End of life for REST API Keys

Fri, 17 Jan 2025 00:00:00 +0000

Effective March 01, 2025, our REST API v2 will no longer accept REST API Keys.

Background

REST API keys are account-level keys and are not directly linked to an individual user, which limits auditing capabilities. This poses a security risk for both New Relic and our customers. User API keys are a well-tested alternative and serve as a replacement to REST API keys. These newer keys can be used across New Relic features such as NerdGraph, among others.

What's happening

Customers using deprecated REST API keys will be impacted by this end-of-life.
If you have integrations or custom scripts which make calls to (api.newrelic.com/v2 or api.eu.newrelic.com/v2) you must check your API keys.
If your API key starts with NRAK, no update is required.

What do you need to do

Generate a new User API key and configure your systems to use it.
If you use a third-party integration, follow the instructions provided by the vendor to update the key.

What happens if you don't make any changes to your account

Failure to update the key will cause API calls to fail against the REST v2 API.
The impact on your operations depends on which REST v2 API endpoints you use and your reliance on them.

Deprecation notice: Kubernetes

Mon, 24 Mar 2025 00:00:00 +0000

Effective Monday, March 3, 2025, our Kubernetes integration will not support Kubernetes v1.27 and earlier. The Kubernetes integration v3.40.1 and later will be compatible only with Kubernetes versions 1.28 and later. For more information, read this note or contact your account team.

Background

Enabling compatibility with the latest Kubernetes versions and adding new features to our Kubernetes offering prevents us from offering first-class support to versions v1.27 and earlier.

What's happening

Most major Kubernetes cloud providers have already deprecated v1.27 and earlier.

What do you need to do

It's easy: Upgrade your Kubernetes clusters to a supported version.

What happens if you don't make any changes to your account

The Kubernetes integration may continue to work with unsupported versions. However, we can't guarantee the quality of the solution as new releases may cause some incompatibilities.

Please note that we won't accept support requests for these versions that have reached the end of life stage.

Change to data exploration

Tue, 01 Apr 2025 00:00:00 +0000

Effective April 30, 2025, our Data Exploration products will no longer be accessible via Query Your Data capability. Instead, you can access the query builder and data explorer by expanding the query console at the bottom of the platform UI.

Background

We are implementing updates to streamline access to our data exploration tools across the platform, including providing additional querying and data exploration features.

What's happening

The Query Your Data capability will be removed from the menu. The legacy Query Builder and Data Explorer that are part of the Query Your Data capability will no longer be accessible.
Query Builder and Data Explorer will now be accessible through the console located at the bottom of the platform.
PromQL query support will be integrated into the query console, allowing you to explore multiple PromQL queries simultaneously using multiple query tabs.

What do you need to do

For accessing Query Builder and Data Explorer: No action required from your side. You can access these tools through the console at the bottom of the platform UI.
For querying with PromQL: Use the PromQL to NRQL translator found in the three-dot menu (kebab menu) within the new query console. Remember, the old Query Builder will not be available after April 30, 2025.

End of Life Announcement: Metrics and Events Explorer

Wed, 07 May 2025 00:00:00 +0000

Effective June 16th, 2025, New Relic will deprecate the following data exploration user interfaces:

The Metrics and Events capability
Metrics Explorer and Events Explorer within entity views

Instead, users can access the query builder and data explorer by expanding the query console at the bottom of the platform UI.

Background

We are committed to enhancing your data querying experiences by streamlining our data exploration tools across the platform. This initiative is aimed at consolidating query building and data exploration into a unified, convenient location, thereby allowing us to innovate and enrich these functionalities further.

What's happening

Deprecation details

Metrics and Events Capability: This will be removed from the left menu.
Metrics Explorer and Events Explorer: These will no longer be accessible from the menus on specific entities.

New access points

The features previously found in the deprecated tools will be available through the Query Console located at the bottom of the platform UI. Our new data explorer includes an intuitive, resizable point-and-click interface to seamlessly understand metrics, timeslices, events, and logs. You will be able to modify queries directly with the shared console between the Query Builder and the Data Explorer.

What do you need to do

No action is required from your side. You can now access the query builder and data explorer through the query console at the bottom of the platform UI.

Attention Required - Upcoming End-of-Life Changes

Mon, 21 Jul 2025 00:00:00 +0000

We are committed to continually improving your experience with our platform, and as part of this effort, we will be retiring or modifying certain features over the coming weeks. These changes are designed to streamline your interactions and enhance the overall functionality of our services.

End-of-Life Updates

Invite a Teammate Feature

What’s Changing: The ability for all users to invite teammates will be modified on Tuesday, October 28, 2025 to only allow Authentication Domain Managers to invite and add users.
Why: This will reduce unnecessary notifications and help to strengthen customer security practices around access controls when adding users to an existing organization.
Impact: Users will need to contact Authentication Domain Managers for user invitations. No additional action is required from customers.

We encourage customers to regularly update to the most current versions of New Relic agents to avoid potential issues and maintain optimal functionality and security.

We understand that changes can sometimes be challenging, but these updates are necessary to help ensure an efficient and secure platform. Our Support team is here to assist you during this transition. If you have any questions about these changes, please contact support.

Thank you for your understanding and support as we work to improve your experience.

End of Life announcement for Node.js 16 and Chrome 134 runtimes used in synthetic monitors: Update Forthcoming

Wed, 05 Nov 2025 00:00:00 +0000

Regarding the recent End-of-Life announcement about ending our support for Chrome 134 and Node.js 16 synthetics runtimes, we will be publishing an updated comprehensive communication shortly. Please stand by for the official update.

In the meantime, if you have already begun testing or upgrading your monitors to the new runtimes (Chrome 140 and Node.js 22) and encountered any specific issues, please let our support team know. It will help us better assist you with the upcoming runtime migration.

End of Life Announcement: Pre-insights APM legacy embedded charts

Mon, 17 Nov 2025 00:00:00 +0000

We’re reaching out to inform you about an important change regarding the removal of APM Legacy Embedded Charts.

What are APM legacy embedded charts?

The embedded chart feature of the original New Relic RPM site allowed users to create a standalone version of a chart displayed in the UI. This standalone chart could be loaded by unauthenticated users and could be embedded in other sites, often dashboards or summary pages.

When New Relic launched the new user experience, we updated this functionality for users for the new platform. Previously created charts have remained accessible since then, and they can be identified by looking at the URL of the chart link. These legacy charts have a url pattern like: https://rpm.newrelic.com/public/charts/<key>

Overview of changes

As part of our continued efforts to enhance security and reliability, we're retiring APM legacy embedded charts. These public charts, created through the now deprecated legacy APM experience, have remained accessible through public URLs, which may also be embedded into external websites and applications. We are preparing to deprecate this service, which will result in the affected links failing to display the chart's data effective June 30, 2026. To replace them with updated New Relic charts, learn how to share charts externally.

Note: This change only affects charts shared publicly via external URLs. It doesn't impact charts viewed within New Relic.

Failure to create replacement embedded charts may lead to missing out on the information in those APM legacy embedded charts. We advise that you take this opportunity to explore the embedded chart links to create replacement charts in order to continue accessing data.

Impact by account type

Effective June 30, 2026, the legacy embedded charts feature will be retired, and all legacy URLs will expire for all users.

For Pro & Enterprise Accounts: Your legacy charts will stop working. You can manually recreate them using the new embedded charts feature, which is already available to you.
For Free & Standard Accounts: Your legacy charts will stop working. The new embedded charts feature is not available on your current tier.
Action Required for Free & Standard Accounts: To continue using embedded charts, you must upgrade to a Pro or Enterprise account and recreate your charts using the new feature.

What do you need to do

Follow the instructions here to enable the functionality to share charts publicly in your account
Since the legacy charts do not show the query used to create them, you’ll need to:
- Navigate to your APM & Services page
  - Explore the available charts to find a match for your legacy chart
  - Click the ellipsis (three dots) and select Get Chart Link

If a match is not found, but you know what data was being queried, then you can try and replicate the query in Data Explorer (Query Your Data):
- Run the query and select the type of chart to use
- Click the ellipsis and select Get Chart Link

Additional support

Our support team is here to assist you during this transition. Please know that we’re committed to supporting you throughout this process. If you have any questions or need further assistance, please don't hesitate to reach out to our support team.

End of Life Announcement: FACET on messageId and timestamp in Alert Conditions

Thu, 10 Jul 2025 00:00:00 +0000

Effective immediately, New Relic is deprecating the ability to create or modify alert conditions with FACET by messageId or timestamp. We have taken this step to protect our systems and customers from unintended impact, as well as keep our customers from violating our acceptable use policy.

Background

In May 2025, New Relic teams were alerted to several alert conditions which were generating many thousands of violations per minute, causing significant traffic for the New Relic service responsible for violation expiration. During service interruptions of this kind of nature, in order to protect New Relic systems and our customers, it is possible that alerts may be unavailable.

After further investigation, New Relic teams determined that thousands of violations were being generated due to these conditions using a FACET clause on the messageId or timestamp attribute. Due to an increase in logs forwarded by the customer at the time, the number of concurrent evaluations for these conditions increased exponentially.

What's changing

Users will no longer be able to create or modify alert conditions with FACET by messageId or timestamp. To be able to view each individual log event from a notification based on an alert condition, use the workflow enrichment feature to write a query using the uniques function to supplement your notification with individual message IDs or timestamps. The existing alert conditions with the mentioned facets will continue to function as expected.

What do you need to do

For more information about limits and rules, view the following articles:

What you need to know

To keep our systems ready to support you and prevent unintended use, we may apply rate limiting if New Relic detects significant resource exhaustion from traffic floods linked to a single account or organization. In these rare cases, and with any other limit incidents, we’ll publish an event to NrIntegrationError, and you can find more information in the limits UI.

End of Life: 32-bit Windows Binaries for Infrastructure Agent

Thu, 04 Dec 2025 00:00:00 +0000

As of Infrastructure Agent version 1.71.2 (released December 4, 2025), New Relic has discontinued the creation of 32-bit Windows binaries for the Infrastructure Agent and Native On-Host Integrations.

What Changed

Creation of 32-bit Windows binaries has been discontinued. All releases from version 1.71.2 onward only support x64 Windows binaries.

Why This Change Was Made

This change aligns with Microsoft's EOL date of Windows 10, which was the last supported OS that had earlier been available in a 32-bit x86 version. Our focus remains on supporting modern and secure operating systems.

Impact

Customers using Windows 10 (32-bit) will no longer be able to upgrade to infrastructure agent versions 1.71.2 or later
Existing installations of earlier versions will continue to function
Customers on actively supported Windows versions, including all modern Windows Server OS editions, are already on 64-bit versions
Customers on any OS that is beyond its vendor's EOL date are expected to upgrade to an OS version that is actively supported
The old 32-bit binaries created before version 1.71.2 will no longer be covered by New Relic's Support team assistance but will be available for downloading if needed

Documentation and Resources

We encourage customers to regularly update to the most current versions of New Relic agents to maintain optimal functionality and security.

End of Life Announcement: Drop Filter Rules API

Wed, 21 May 2025 00:00:00 +0000

Effective June 30, 2026 16:00 UTC, the NRQL Drop Filter Rules API will be discontinued and fully replaced by the Pipeline cloud rules API. Your existing NRQL drop filter rules will be automatically migrated. However, you'll need to take action to ensure a smooth transition to the new cloud rules API.

Background

This update is part of our ongoing work to improve our platform and streamline our APIs. This helps us ensure continued innovation and a more sustainable system. The new Pipeline cloud rules API, integrated with Pipeline Control, offers the same functionality as the old API. It also works with the next-generation New Relic Control system, providing a more robust, consistent, and unified experience.

What's changing

The NRQL Drop Filter Rules API will be deprecated and shut off on June 30, 2026.
As of June 30, 2026, you must use the Pipeline cloud rules API, or the centralized Pipeline Control UI, for all drop rule creation and management.
On February 3, 2026, drop rules targeting infrastructure events in SystemSample, ProcessSample, NetworkSample, and StorageSample will also correctly drop aggregated data.
Renewals after the effective date will require the use of Pipeline cloud rules API, which is available with the Advanced Compute add-on.

What do you need to do

Maintain your data drop needs by:
- Updating your integrations and references to the new Pipeline Cloud Rules API by June 30, 2026.
- Using Pipeline Control gateway to drop data before it leaves your environment, with the added benefits of no egress costs for data dropped and upcoming enhancements including Dynamic DT Sampling and routing.
Do not migrate your drop rules. New Relic will handle the move from the old NRQL Drop Filter Rules API to the Pipeline cloud rules API.
Access a unified rules list in June 2025 for migration assistance and visibility across both APIs.
Add Advanced Compute before June 30, 2026 (if you are on Pay As You Go) to maintain uninterrupted use of drop rules.
Upgrade to a paid plan (if you are on the free tier) to continue using drop rules after the effective date.

If no action is taken

As of June 30th, 2026, calls to NRQL Drop Filter Rules API will fail i.e. no rules can be created or deleted. Migrate to Pipeline cloud rules API before then.
If you are on Pay As You Go or free tier, drop rules will be disabled if your account is not on Advanced Compute before June 30, 2026. After the EOL date using Pipeline Control Cloud Rules drop data will generate aCCU usage.
If you have a commitment contract, work with your account team to add Advanced Compute before your next renewal to ensure continuous rule processing and authoring. Otherwise, rule creation will be disabled, and existing rules will be turned off at your renewal. After the EOL date when you renew, using Pipeline Control Cloud Rules drop data will generate aCCU usage.

Next steps

Review your current use of NRQL Drop Filter Rules API.
Begin planning your migration to the Pipeline cloud rules API.
All rules are now visible from either API to help you migrate to the Pipeline Control API.
Contact your New Relic representative or support for assistance with migration or to discuss your options.

We understand that changes to capabilities can be disruptive, and we are committed to supporting you through this transition. Our goal is to provide ample time and resources to ensure a smooth migration with minimal impact to your workflows.

Our support team is here to assist you during this transition. If you have any questions about these changes, please contact Support or reach out to your account team. To learn more about the advantages of Pipeline Control UI, check out New Relic Pipeline Control.

Thank you for your partnership and understanding as we continue to improve our platform and services.