From 531ab71e6db627b13b955996eef08b3255566fd2 Mon Sep 17 00:00:00 2001 From: Keegan Mullaney Date: Mon, 11 Aug 2025 19:49:08 -0700 Subject: [PATCH 1/6] docs: add entity tags restriction Tags on cloud entities cannot be used in a WHERE clause in a drop rule because they are not part of the data when the drop rule is evaluated. Metric Streams does not send entity tags along with metric data. --- .../new-relic-control/pipeline-control/cloud-rules-api.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx index 42d8b1b1f34..fe00b6ec2f9 100644 --- a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx +++ b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx @@ -54,7 +54,8 @@ Use cloud rules to target the following data types: * The limit on NRQL query length is **4096** characters. If it exceeds the length, the `INVALID_NRQL_TOO_LONG` error occurs. If you need to drop data based on a longer query that cannot be split, contact your [New Relic support](https://support.newrelic.com). * `JOIN` and [subqueries](/docs/query-your-data/nrql-new-relic-query-language/get-started/subqueries-in-nrql) are not supported. -* You can provide a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to select data with specific attributes. +* You can provide a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to select data with specific attributes +* You can't use entity tags in a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to drop data because entity tags are fetched in a separate process and are not part of the data when the pipeline rule is evaluated. * Features such as `LIMIT`, `TIMESERIES`, `COMPARE WITH`, `FACET`, and other clauses cannot be used. * `SINCE` and `UNTIL` are not supported. If you have time-specific rules (say, drop everything until a time in the future), use `WHERE timestamp < (epoch milliseconds in the future)`. * You can't use `SINCE` to drop historical data. Cloud rules only apply to data reported after the rule was created. If you need to delete data that has already been reported, refer to [Delete existing data](/docs/data-apis/manage-data/manage-data-retention/#deleting-data) or contact [New Relic support](https://support.newrelic.com). From a3c12f2f905efd68814f97af11752a97aa7c818d Mon Sep 17 00:00:00 2001 From: Keegan Mullaney Date: Mon, 11 Aug 2025 19:54:57 -0700 Subject: [PATCH 2/6] docs: fix period --- .../docs/new-relic-control/pipeline-control/cloud-rules-api.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx index fe00b6ec2f9..19f555882b7 100644 --- a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx +++ b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx @@ -54,7 +54,7 @@ Use cloud rules to target the following data types: * The limit on NRQL query length is **4096** characters. If it exceeds the length, the `INVALID_NRQL_TOO_LONG` error occurs. If you need to drop data based on a longer query that cannot be split, contact your [New Relic support](https://support.newrelic.com). * `JOIN` and [subqueries](/docs/query-your-data/nrql-new-relic-query-language/get-started/subqueries-in-nrql) are not supported. -* You can provide a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to select data with specific attributes +* You can provide a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to select data with specific attributes. * You can't use entity tags in a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to drop data because entity tags are fetched in a separate process and are not part of the data when the pipeline rule is evaluated. * Features such as `LIMIT`, `TIMESERIES`, `COMPARE WITH`, `FACET`, and other clauses cannot be used. * `SINCE` and `UNTIL` are not supported. If you have time-specific rules (say, drop everything until a time in the future), use `WHERE timestamp < (epoch milliseconds in the future)`. From ba02d3ef9023face2cf2a0e3afc6f19235d8a1c2 Mon Sep 17 00:00:00 2001 From: Keegan Mullaney Date: Mon, 11 Aug 2025 19:57:28 -0700 Subject: [PATCH 3/6] docs: reword --- .../docs/new-relic-control/pipeline-control/cloud-rules-api.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx index 19f555882b7..9e3df962e46 100644 --- a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx +++ b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx @@ -55,7 +55,7 @@ Use cloud rules to target the following data types: * The limit on NRQL query length is **4096** characters. If it exceeds the length, the `INVALID_NRQL_TOO_LONG` error occurs. If you need to drop data based on a longer query that cannot be split, contact your [New Relic support](https://support.newrelic.com). * `JOIN` and [subqueries](/docs/query-your-data/nrql-new-relic-query-language/get-started/subqueries-in-nrql) are not supported. * You can provide a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to select data with specific attributes. -* You can't use entity tags in a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to drop data because entity tags are fetched in a separate process and are not part of the data when the pipeline rule is evaluated. +* You can't use entity tags in a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to drop data, because entity tags are fetched in a separate process and are not part of the dataset evaluated by the pipeline rule. * Features such as `LIMIT`, `TIMESERIES`, `COMPARE WITH`, `FACET`, and other clauses cannot be used. * `SINCE` and `UNTIL` are not supported. If you have time-specific rules (say, drop everything until a time in the future), use `WHERE timestamp < (epoch milliseconds in the future)`. * You can't use `SINCE` to drop historical data. Cloud rules only apply to data reported after the rule was created. If you need to delete data that has already been reported, refer to [Delete existing data](/docs/data-apis/manage-data/manage-data-retention/#deleting-data) or contact [New Relic support](https://support.newrelic.com). From e718aa687bd301bef074a38abb5d9b1bab191b30 Mon Sep 17 00:00:00 2001 From: Keegan Mullaney Date: Mon, 11 Aug 2025 19:59:16 -0700 Subject: [PATCH 4/6] docs: minor fix --- .../docs/new-relic-control/pipeline-control/cloud-rules-api.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx index 9e3df962e46..e3c4906c266 100644 --- a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx +++ b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx @@ -55,7 +55,7 @@ Use cloud rules to target the following data types: * The limit on NRQL query length is **4096** characters. If it exceeds the length, the `INVALID_NRQL_TOO_LONG` error occurs. If you need to drop data based on a longer query that cannot be split, contact your [New Relic support](https://support.newrelic.com). * `JOIN` and [subqueries](/docs/query-your-data/nrql-new-relic-query-language/get-started/subqueries-in-nrql) are not supported. * You can provide a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to select data with specific attributes. -* You can't use entity tags in a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to drop data, because entity tags are fetched in a separate process and are not part of the dataset evaluated by the pipeline rule. +* You can't use entity tags in a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to drop data, because entity tags are fetched in a separate process and are not part of the dataset evaluated by the pipeline cloud rule. * Features such as `LIMIT`, `TIMESERIES`, `COMPARE WITH`, `FACET`, and other clauses cannot be used. * `SINCE` and `UNTIL` are not supported. If you have time-specific rules (say, drop everything until a time in the future), use `WHERE timestamp < (epoch milliseconds in the future)`. * You can't use `SINCE` to drop historical data. Cloud rules only apply to data reported after the rule was created. If you need to delete data that has already been reported, refer to [Delete existing data](/docs/data-apis/manage-data/manage-data-retention/#deleting-data) or contact [New Relic support](https://support.newrelic.com). From 33f2782fa5f706769555c84553e1b4d86fc6a88d Mon Sep 17 00:00:00 2001 From: Keegan Mullaney Date: Tue, 12 Aug 2025 08:53:31 -0700 Subject: [PATCH 5/6] docs: wording --- .../docs/new-relic-control/pipeline-control/cloud-rules-api.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx index e3c4906c266..f5a49ec2e90 100644 --- a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx +++ b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx @@ -55,7 +55,7 @@ Use cloud rules to target the following data types: * The limit on NRQL query length is **4096** characters. If it exceeds the length, the `INVALID_NRQL_TOO_LONG` error occurs. If you need to drop data based on a longer query that cannot be split, contact your [New Relic support](https://support.newrelic.com). * `JOIN` and [subqueries](/docs/query-your-data/nrql-new-relic-query-language/get-started/subqueries-in-nrql) are not supported. * You can provide a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to select data with specific attributes. -* You can't use entity tags in a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to drop data, because entity tags are fetched in a separate process and are not part of the dataset evaluated by the pipeline cloud rule. +* You shouldn't use entity tags in a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to drop data, because entity tags are fetched in a separate process and are not part of the dataset evaluated by the pipeline cloud rule. * Features such as `LIMIT`, `TIMESERIES`, `COMPARE WITH`, `FACET`, and other clauses cannot be used. * `SINCE` and `UNTIL` are not supported. If you have time-specific rules (say, drop everything until a time in the future), use `WHERE timestamp < (epoch milliseconds in the future)`. * You can't use `SINCE` to drop historical data. Cloud rules only apply to data reported after the rule was created. If you need to delete data that has already been reported, refer to [Delete existing data](/docs/data-apis/manage-data/manage-data-retention/#deleting-data) or contact [New Relic support](https://support.newrelic.com). From b0c95753e4f4c26ef7bef0f3bf35aa356e156245 Mon Sep 17 00:00:00 2001 From: Keegan Mullaney Date: Tue, 12 Aug 2025 11:48:01 -0700 Subject: [PATCH 6/6] docs: be specific --- .../docs/new-relic-control/pipeline-control/cloud-rules-api.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx index f5a49ec2e90..2729aad328d 100644 --- a/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx +++ b/src/content/docs/new-relic-control/pipeline-control/cloud-rules-api.mdx @@ -55,7 +55,7 @@ Use cloud rules to target the following data types: * The limit on NRQL query length is **4096** characters. If it exceeds the length, the `INVALID_NRQL_TOO_LONG` error occurs. If you need to drop data based on a longer query that cannot be split, contact your [New Relic support](https://support.newrelic.com). * `JOIN` and [subqueries](/docs/query-your-data/nrql-new-relic-query-language/get-started/subqueries-in-nrql) are not supported. * You can provide a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to select data with specific attributes. -* You shouldn't use entity tags in a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to drop data, because entity tags are fetched in a separate process and are not part of the dataset evaluated by the pipeline cloud rule. +* You shouldn't use entity tags in a [`WHERE`](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-clauses-functions#sel-where) clause to drop data, because entity tags are fetched in a separate process and are not attributes of the MELT data evaluated by the pipeline cloud rule. * Features such as `LIMIT`, `TIMESERIES`, `COMPARE WITH`, `FACET`, and other clauses cannot be used. * `SINCE` and `UNTIL` are not supported. If you have time-specific rules (say, drop everything until a time in the future), use `WHERE timestamp < (epoch milliseconds in the future)`. * You can't use `SINCE` to drop historical data. Cloud rules only apply to data reported after the rule was created. If you need to delete data that has already been reported, refer to [Delete existing data](/docs/data-apis/manage-data/manage-data-retention/#deleting-data) or contact [New Relic support](https://support.newrelic.com).