Skip to content

Nr 416540 drop rule eol content #20713

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 21, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,12 @@ redirects:
freshnessValidatedDate: never
---

<Callout variant="important">
As of May 21, 2025, new customers can no longer use NRQL drop rules. Leverage [New Relic Pipeline Control](/docs/new-relic-control/pipeline-control/overview/). Pipeline cloud rules are the direct replacement of NRQL drop rules, and pipeline gateway can also help manage data.

[NRQL drop rules will be end of life](/eol/2025/06/drop-rule-filter) January 7, 2026.
</Callout>

One way to [manage your data ingest](/docs/data-apis/manage-data/manage-data-coming-new-relic) is to set up data dropping rules. With data dropping you can:

* Filter out unimportant low-value data
Expand Down
6 changes: 6 additions & 0 deletions src/content/docs/logs/ui-data/drop-data-drop-filter-rules.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,12 @@ redirects:
freshnessValidatedDate: never
---

<Callout variant="important">
As of May 21, 2025, new customers can no longer use NRQL drop rules via the logs management UI. Leverage [New Relic Pipeline Control](/docs/new-relic-control/pipeline-control/overview). Pipeline cloud rules are the direct replacement of NRQL drop rules, and pipeline gateway can also help manage data.

[NRQL drop rules will be end of life](/eol/2025/06/drop-rule-filter) January 7, 2026.
</Callout>

After log event data has been sent to New Relic, it can either be stored in our NRDB database or dropped (discarded). To drop log data, you can use the logs management UI, as explained in this document. You can also use [NerdGraph to drop data](/docs/accounts/accounts/data-management/drop-data-using-nerdgraph). NerdGraph is our GraphQL Explorer.

## Savings, security, speed [#why-it-matters]
Expand Down
42 changes: 42 additions & 0 deletions src/content/eol/2025/05/drop-rule-filter.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
---
title: 'End of Life Announcement: Drop Filter Rules API'
subject: EOL for Drop Filter Rules API
publishDate: '2025-05-21'

Check warning on line 4 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L4

[new-relic.RangeFormat] Use an en dash in a range of numbers.
Raw output
{"message": "[new-relic.RangeFormat] Use an en dash in a range of numbers.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 4, "column": 15}}}, "severity": "WARNING"}
eolEffectiveDate: '2026-01-07'

Check warning on line 5 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L5

[new-relic.RangeFormat] Use an en dash in a range of numbers.
Raw output
{"message": "[new-relic.RangeFormat] Use an en dash in a range of numbers.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 5, "column": 20}}}, "severity": "WARNING"}
---

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.

Check notice on line 8 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L8

[Microsoft.Passive] 'be discontinued' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'be discontinued' looks like passive voice.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 8, "column": 64}}}, "severity": "INFO"}

Check notice on line 8 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L8

[Microsoft.Wordiness] Consider using 'act' instead of 'take action'.
Raw output
{"message": "[Microsoft.Wordiness] Consider using 'act' instead of 'take action'.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 8, "column": 286}}}, "severity": "INFO"}

## Background [#bg]

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](/docs/new-relic-control/pipeline-control/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 [#whats-changing]
* The NRQL Drop Filter Rules API will be deprecated and shut off on January 7, 2026.

Check notice on line 15 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L15

[Microsoft.Passive] 'be deprecated' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'be deprecated' looks like passive voice.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 15, "column": 39}}}, "severity": "INFO"}
* After January 7, 2026, you must use the [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/), or the Pipeline Control UI, for all drop rule creation and management.
* Renewals after January 7, 2026 will require the use of [Pipeline cloud rules API](/docs/new-relic-control/pipeline-control/cloud-rules-api/), which is available with the [Advanced Compute add-on](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/add-on-billing/).

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

* Update your integrations and references to the new Pipeline Cloud Rules API by January 7, 2026.
* 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/).

Check failure on line 22 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L22

[Microsoft.Contractions] Use 'don't' instead of 'Do not'.
Raw output
{"message": "[Microsoft.Contractions] Use 'don't' instead of 'Do not'.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 22, "column": 3}}}, "severity": "ERROR"}
* Access a unified rules list in June 2025 for migration assistance and visibility across both APIs.

Check notice on line 23 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L23

[new-relic.ComplexWords] Consider using 'help' instead of 'assistance'.
Raw output
{"message": "[new-relic.ComplexWords] Consider using 'help' instead of 'assistance'.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 23, "column": 58}}}, "severity": "INFO"}
* 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.

Check notice on line 24 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L24

[new-relic.ComplexWords] Consider using 'keep' or 'support' instead of 'maintain'.
Raw output
{"message": "[new-relic.ComplexWords] Consider using 'keep' or 'support' instead of 'maintain'.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 24, "column": 162}}}, "severity": "INFO"}
* 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 [#no-action]

Check notice on line 27 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L27

[Microsoft.Passive] 'is taken' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'is taken' looks like passive voice.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 27, "column": 17}}}, "severity": "INFO"}
* 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.
* 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.

Check notice on line 29 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L29

[Microsoft.Passive] 'be disabled' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'be disabled' looks like passive voice.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 29, "column": 147}}}, "severity": "INFO"}

Check failure on line 29 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L29

[Microsoft.Contractions] Use 'isn't' instead of 'is not'.
Raw output
{"message": "[Microsoft.Contractions] Use 'isn't' instead of 'is not'.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 29, "column": 175}}}, "severity": "ERROR"}
* 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.

Check notice on line 30 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L30

[Microsoft.Passive] 'be disabled' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'be disabled' looks like passive voice.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 30, "column": 197}}}, "severity": "INFO"}

Check notice on line 30 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L30

[Microsoft.Passive] 'be turned' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'be turned' looks like passive voice.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 30, "column": 234}}}, "severity": "INFO"}

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

Check notice on line 36 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L36

[new-relic.ComplexWords] Consider using 'help' instead of 'assistance'.
Raw output
{"message": "[new-relic.ComplexWords] Consider using 'help' instead of 'assistance'.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 36, "column": 56}}}, "severity": "INFO"}

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.

Check failure on line 38 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L38

[Microsoft.Contractions] Use 'we're' instead of 'we are'.
Raw output
{"message": "[Microsoft.Contractions] Use 'we're' instead of 'we are'.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 38, "column": 67}}}, "severity": "ERROR"}

Check notice on line 38 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L38

[Microsoft.Passive] 'are committed' looks like passive voice.
Raw output
{"message": "[Microsoft.Passive] 'are committed' looks like passive voice.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 38, "column": 70}}}, "severity": "INFO"}

Check notice on line 38 in src/content/eol/2025/05/drop-rule-filter.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/content/eol/2025/05/drop-rule-filter.md#L38

[new-relic.ComplexWords] Consider using 'give' or 'offer' instead of 'provide'.
Raw output
{"message": "[new-relic.ComplexWords] Consider using 'give' or 'offer' instead of 'provide'.", "location": {"path": "src/content/eol/2025/05/drop-rule-filter.md", "range": {"start": {"line": 38, "column": 142}}}, "severity": "INFO"}

Our support team is here to assist you during this transition. If you have any questions about these changes, please [contact Support](/docs/new-relic-solutions/solve-common-issues/find-help-get-support/) or reach out to your account team. To learn more about the advantages of Pipeline Control UI, check out [New Relic Pipeline Control](https://newrelic.com/platform/pipeline-control).

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