Skip to content

Commit e19ebc4

Browse files
Merge pull request #20780 from newrelic/updates-to-drop-rules-eol
chore(drop-rules-eol): updates
2 parents 9318891 + 67ebee6 commit e19ebc4

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

src/content/eol/2025/05/drop-rule-filter.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ publishDate: '2025-05-21'
55
eolEffectiveDate: '2026-01-07'
66
---
77

8-
Effective January 7, 2026, the NRQL Drop Filter Rules API will be discontinued and fully replaced by the [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/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.
8+
Effective January 7, 2026 16:00 UTC, the NRQL Drop Filter Rules API will be discontinued and fully replaced by the [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/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.
99

1010
## Background [#bg]
1111

@@ -18,22 +18,24 @@ This update is part of our ongoing work to improve our platform and streamline o
1818

1919
## What do you need to do [#what-to-do]
2020

21-
* Update your integrations and references to the new Pipeline Cloud Rules API by January 7, 2026.
21+
* Maintain your data drop needs by:
22+
- Updating your integrations and references to the new [Pipeline Cloud Rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/) by January 7, 2026.
23+
- 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.
2224
* 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](/docs/new-relic-control/pipeline-control/cloud-rules-api/).
2325
* Access a unified rules list in June 2025 for migration assistance and visibility across both APIs.
2426
* Add Advanced Compute by January 7, 2026 (if you are on [Pay As You Go](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/#pay-as-you-go)) to maintain uninterrupted use of drop rules.
2527
* Upgrade to a paid plan (if you are on the free tier) to continue using drop rules after the effective date.
2628

2729
## If no action is taken [#no-action]
28-
* After January 7th, 2026, calls to NRQL Ddrop Filter Rrules API will fail. Migrate to [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/) by then.
30+
* After January 7th, 2026, calls to NRQL Drop Filter Rrules API will fail. Migrate to [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/) by then.
2931
* If you are on [Pay As You Go](/docs/licenses/license-information/usage-plans/new-relic-usage-plan/#pay-as-you-go) or free tier, drop rules will be disabled if your account is not on Advanced Compute at the next renewal after January 7th, 2026.
3032
* 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.
3133

3234
## Next steps
33-
* Review your current use of NRQL Drop Filter Rules API.
34-
* Begin planning your migration to the [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/).
35-
* Watch for communications regarding the unified rules list and migration tools, coming June 2025.
36-
* Contact your New Relic representative or support for assistance with migration or to discuss your options.
35+
1. Review your current use of NRQL Drop Filter Rules API.
36+
2. Begin planning your migration to the [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/).
37+
3. Watch for communications regarding the unified rules list and migration tools, coming June 2025.
38+
4. Contact your New Relic representative or support for assistance with migration or to discuss your options.
3739

3840
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.
3941

0 commit comments

Comments
 (0)