From 8232816c335430fddde59991bd32273e67939fbc Mon Sep 17 00:00:00 2001 From: Haus Owens <98408+haus@users.noreply.github.com> Date: Tue, 29 Oct 2024 12:44:08 -0700 Subject: [PATCH 1/6] (NR-320588) Adding some documentation for a new query limit We are adding a new limit that will be enforced on alert query registration, so this commit adds some documentation around the default limit and adds some pointers on working with it. --- .../docs/alerts/admin/rules-limits-alerts.mdx | 38 ++++++++++++++++++- 1 file changed, 36 insertions(+), 2 deletions(-) diff --git a/src/content/docs/alerts/admin/rules-limits-alerts.mdx b/src/content/docs/alerts/admin/rules-limits-alerts.mdx index 8e8663e24d0..788ad15a862 100644 --- a/src/content/docs/alerts/admin/rules-limits-alerts.mdx +++ b/src/content/docs/alerts/admin/rules-limits-alerts.mdx @@ -107,6 +107,20 @@ Limits and rules pertaining to New Relic : + + + Alerts query scan operations per minute, per account ([learn more](#query-scan-limit)) + + + + N/A + + + + 2,500,000,000 + + + [Condition name](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-alert-conditions) @@ -330,8 +344,8 @@ You can see your matched data points and any limit incidents in the [limits UI]( To understand what conditions are leading to the most throughput, you can perform a query like: ```sql -FROM NrAiSignal -SELECT sum(aggregatedDataPointsCount) AS 'alert matched data points' +FROM NrAiSignal +SELECT sum(aggregatedDataPointsCount) AS 'alert matched data points' FACET conditionId ``` @@ -344,3 +358,23 @@ Some tips on optimizing your matched data points: To request a limit increase, talk to your New Relic account representative. Note that using [sliding windows](/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/create-smoother-charts-sliding-windows) can significantly increase the number of data points. Consider using a longer duration of Sliding window aggregation to reduce the number of data points produced. + +## Alerts query scan operations per minute [#query-scan-limit] + +The alert condition `Alerts query scan operations per minute` limit applies to the total rate of query scan operations on ingested events. +A query scan operation is the work performed by the New Relic pipeline to match ingested events to alert queries registered in a New Relic [account](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure). + +If this limit is exceeded, you won't be able to create or update conditions for the impacted account until the rate goes below the limit. Existing alert conditions are **not** affected. + +You can see your query scan operations and any limit incidents in the [limits UI](/docs/data-apis/manage-data/view-system-limits). + +When matching events to alert queries, all events from the [data type](/docs/nrql/get-started/introduction-nrql-new-relics-query-language/#what-you-can-query) that the query references must be examined. Here are a few common ways to have fewer events in a given data type (which will decrease the alert query scan operations): +* When alerting on Logs data, use [log partitions](/docs/tutorial-manage-large-log-volume/organize-large-logs/) to limit which logs are being scanned for alert queries. +* When alerting on Custom Events, break up larger custom event types +* Use Custom Events instead of alerting on Transaction events +* [Create metrics](/docs/data-apis/convert-to-metrics/create-metrics-other-data-types/) when possible +* Use [metric timeslice queries](/docs/data-apis/understand-data/metric-data/query-apm-metric-timeslice-data-nrql/) when possible instead of alerting on Transaction + +In addition to the above tips, cleaning up any unused or unneeded alert queries (alert conditions) will decrease the number of query scan operations. + +To request a limit increase, talk to your New Relic account representative. From dfaf848a225f081e0fa17018f9ac66421ba4dfdc Mon Sep 17 00:00:00 2001 From: Haus Owens <98408+haus@users.noreply.github.com> Date: Tue, 29 Oct 2024 12:56:34 -0700 Subject: [PATCH 2/6] Alerts -> alert to match actual limit name --- src/content/docs/alerts/admin/rules-limits-alerts.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/alerts/admin/rules-limits-alerts.mdx b/src/content/docs/alerts/admin/rules-limits-alerts.mdx index 788ad15a862..a95194c54ad 100644 --- a/src/content/docs/alerts/admin/rules-limits-alerts.mdx +++ b/src/content/docs/alerts/admin/rules-limits-alerts.mdx @@ -109,7 +109,7 @@ Limits and rules pertaining to New Relic : - Alerts query scan operations per minute, per account ([learn more](#query-scan-limit)) + Alert query scan operations per minute, per account ([learn more](#query-scan-limit)) @@ -359,9 +359,9 @@ To request a limit increase, talk to your New Relic account representative. Note that using [sliding windows](/docs/query-your-data/nrql-new-relic-query-language/nrql-query-tutorials/create-smoother-charts-sliding-windows) can significantly increase the number of data points. Consider using a longer duration of Sliding window aggregation to reduce the number of data points produced. -## Alerts query scan operations per minute [#query-scan-limit] +## Alert query scan operations per minute [#query-scan-limit] -The alert condition `Alerts query scan operations per minute` limit applies to the total rate of query scan operations on ingested events. +The alert condition `Alert query scan operations per minute` limit applies to the total rate of query scan operations on ingested events. A query scan operation is the work performed by the New Relic pipeline to match ingested events to alert queries registered in a New Relic [account](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure). If this limit is exceeded, you won't be able to create or update conditions for the impacted account until the rate goes below the limit. Existing alert conditions are **not** affected. From 5980eb9554867019a10640d7ada8f7e313a1f6da Mon Sep 17 00:00:00 2001 From: Haus Owens <98408+haus@users.noreply.github.com> Date: Tue, 29 Oct 2024 13:06:46 -0700 Subject: [PATCH 3/6] Are not -> aren't to satisfy vale checker --- src/content/docs/alerts/admin/rules-limits-alerts.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/alerts/admin/rules-limits-alerts.mdx b/src/content/docs/alerts/admin/rules-limits-alerts.mdx index a95194c54ad..a0164794cc5 100644 --- a/src/content/docs/alerts/admin/rules-limits-alerts.mdx +++ b/src/content/docs/alerts/admin/rules-limits-alerts.mdx @@ -337,7 +337,7 @@ Limits and rules pertaining to New Relic : The alert condition `Matched data points per minute` limit applies to the total rate of matched [data points](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/streaming-alerts-key-terms-concepts) for the alerting queries in a New Relic [account](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure). -If this limit is exceeded, you won't be able to create or update conditions for the impacted account until the rate goes below the limit. Existing alert conditions are **not** affected. +If this limit is exceeded, you won't be able to create or update conditions for the impacted account until the rate goes below the limit. Existing alert conditions **aren't** affected. You can see your matched data points and any limit incidents in the [limits UI](/docs/data-apis/manage-data/view-system-limits). @@ -364,7 +364,7 @@ Note that using [sliding windows](/docs/query-your-data/nrql-new-relic-query-lan The alert condition `Alert query scan operations per minute` limit applies to the total rate of query scan operations on ingested events. A query scan operation is the work performed by the New Relic pipeline to match ingested events to alert queries registered in a New Relic [account](/docs/accounts/accounts-billing/account-structure/new-relic-account-structure). -If this limit is exceeded, you won't be able to create or update conditions for the impacted account until the rate goes below the limit. Existing alert conditions are **not** affected. +If this limit is exceeded, you won't be able to create or update conditions for the impacted account until the rate goes below the limit. Existing alert conditions **aren't** affected. You can see your query scan operations and any limit incidents in the [limits UI](/docs/data-apis/manage-data/view-system-limits). From d4bf2905785b97f0c88e406a23e7feac5bfe8c32 Mon Sep 17 00:00:00 2001 From: Haus Owens <98408+haus@users.noreply.github.com> Date: Tue, 29 Oct 2024 14:01:32 -0700 Subject: [PATCH 4/6] Tweak language in a few bullets --- src/content/docs/alerts/admin/rules-limits-alerts.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/alerts/admin/rules-limits-alerts.mdx b/src/content/docs/alerts/admin/rules-limits-alerts.mdx index a0164794cc5..ab563f45cf4 100644 --- a/src/content/docs/alerts/admin/rules-limits-alerts.mdx +++ b/src/content/docs/alerts/admin/rules-limits-alerts.mdx @@ -372,8 +372,8 @@ When matching events to alert queries, all events from the [data type](/docs/nrq * When alerting on Logs data, use [log partitions](/docs/tutorial-manage-large-log-volume/organize-large-logs/) to limit which logs are being scanned for alert queries. * When alerting on Custom Events, break up larger custom event types * Use Custom Events instead of alerting on Transaction events -* [Create metrics](/docs/data-apis/convert-to-metrics/create-metrics-other-data-types/) when possible -* Use [metric timeslice queries](/docs/data-apis/understand-data/metric-data/query-apm-metric-timeslice-data-nrql/) when possible instead of alerting on Transaction +* [Create metrics](/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics/) to aggregate data +* Use [metric timeslice queries](/docs/data-apis/understand-data/metric-data/query-apm-metric-timeslice-data-nrql/) when possible instead of alerting on Transaction events In addition to the above tips, cleaning up any unused or unneeded alert queries (alert conditions) will decrease the number of query scan operations. From 8adaea7fd54394692ab4efa93af3ff7cfa99afd3 Mon Sep 17 00:00:00 2001 From: Haus <98408+haus@users.noreply.github.com> Date: Wed, 30 Oct 2024 09:39:04 -0700 Subject: [PATCH 5/6] Update src/content/docs/alerts/admin/rules-limits-alerts.mdx Co-authored-by: ally sassman <42753584+ally-sassman@users.noreply.github.com> --- src/content/docs/alerts/admin/rules-limits-alerts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/alerts/admin/rules-limits-alerts.mdx b/src/content/docs/alerts/admin/rules-limits-alerts.mdx index ab563f45cf4..3e6c8737071 100644 --- a/src/content/docs/alerts/admin/rules-limits-alerts.mdx +++ b/src/content/docs/alerts/admin/rules-limits-alerts.mdx @@ -369,7 +369,7 @@ If this limit is exceeded, you won't be able to create or update conditions for You can see your query scan operations and any limit incidents in the [limits UI](/docs/data-apis/manage-data/view-system-limits). When matching events to alert queries, all events from the [data type](/docs/nrql/get-started/introduction-nrql-new-relics-query-language/#what-you-can-query) that the query references must be examined. Here are a few common ways to have fewer events in a given data type (which will decrease the alert query scan operations): -* When alerting on Logs data, use [log partitions](/docs/tutorial-manage-large-log-volume/organize-large-logs/) to limit which logs are being scanned for alert queries. +* When alerting on logs data, use [log partitions](/docs/tutorial-manage-large-log-volume/organize-large-logs/) to limit which logs are being scanned for alert queries. * When alerting on Custom Events, break up larger custom event types * Use Custom Events instead of alerting on Transaction events * [Create metrics](/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics/) to aggregate data From 053d8798c23fa1fa809703b1d8ddf3c17f79ce95 Mon Sep 17 00:00:00 2001 From: a-sassman Date: Wed, 30 Oct 2024 13:45:28 -0700 Subject: [PATCH 6/6] fix(alerts): improve table organization, lowercase event types, add an intro at the top --- .../docs/alerts/admin/rules-limits-alerts.mdx | 141 +++++++++--------- 1 file changed, 68 insertions(+), 73 deletions(-) diff --git a/src/content/docs/alerts/admin/rules-limits-alerts.mdx b/src/content/docs/alerts/admin/rules-limits-alerts.mdx index ab563f45cf4..477a1d7c996 100644 --- a/src/content/docs/alerts/admin/rules-limits-alerts.mdx +++ b/src/content/docs/alerts/admin/rules-limits-alerts.mdx @@ -12,30 +12,32 @@ redirects: - /docs/alerts-applied-intelligence/new-relic-alerts/rules-limits-glossary/rules-limits-new-relic-alerts - /docs/alerts-applied-intelligence/new-relic-alerts/rules-limits-glossary/rules-limits-alerts/ - /docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/rules-limits-alerts -freshnessValidatedDate: never +freshnessValidatedDate: 2024-10-30 --- -Limits and rules pertaining to New Relic : +This page describes limits and rules pertaining to New Relic : + @@ -43,17 +45,9 @@ Limits and rules pertaining to New Relic : - - - - + @@ -68,32 +62,28 @@ Limits and rules pertaining to New Relic : + - - - - @@ -108,6 +98,9 @@ Limits and rules pertaining to New Relic : + @@ -117,11 +110,14 @@ Limits and rules pertaining to New Relic : + @@ -136,6 +132,9 @@ Limits and rules pertaining to New Relic : + @@ -150,8 +149,11 @@ Limits and rules pertaining to New Relic : + + @@ -173,12 +178,15 @@ Limits and rules pertaining to New Relic : + @@ -195,29 +203,25 @@ Limits and rules pertaining to New Relic : - - - - - n/a + N/A + @@ -232,6 +236,9 @@ Limits and rules pertaining to New Relic : + @@ -241,13 +248,16 @@ Limits and rules pertaining to New Relic : + @@ -257,7 +267,7 @@ Limits and rules pertaining to New Relic : - - - - + @@ -301,23 +305,14 @@ Limits and rules pertaining to New Relic : - - - - @@ -369,11 +364,11 @@ If this limit is exceeded, you won't be able to create or update conditions for You can see your query scan operations and any limit incidents in the [limits UI](/docs/data-apis/manage-data/view-system-limits). When matching events to alert queries, all events from the [data type](/docs/nrql/get-started/introduction-nrql-new-relics-query-language/#what-you-can-query) that the query references must be examined. Here are a few common ways to have fewer events in a given data type (which will decrease the alert query scan operations): -* When alerting on Logs data, use [log partitions](/docs/tutorial-manage-large-log-volume/organize-large-logs/) to limit which logs are being scanned for alert queries. -* When alerting on Custom Events, break up larger custom event types -* Use Custom Events instead of alerting on Transaction events -* [Create metrics](/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics/) to aggregate data -* Use [metric timeslice queries](/docs/data-apis/understand-data/metric-data/query-apm-metric-timeslice-data-nrql/) when possible instead of alerting on Transaction events +* When alerting on logs data, use [log partitions](/docs/tutorial-manage-large-log-volume/organize-large-logs/) to limit which logs are being scanned for alert queries. +* When alerting on custom events, break up larger custom event types. +* Use custom events instead of alerting on transaction events. +* [Create metrics](/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics/) to aggregate data. +* Use [metric timeslice queries](/docs/data-apis/understand-data/metric-data/query-apm-metric-timeslice-data-nrql/) when possible instead of alerting on transaction events. In addition to the above tips, cleaning up any unused or unneeded alert queries (alert conditions) will decrease the number of query scan operations.
- + **Category** + + **Limited condition** - + - + **Minimum value** - + - **Maximum value** - +
- - **Alert policies:** - - + Alert policies - -
[Alert policy name](/docs/alerts/organize-alerts/create-edit-or-find-alert-policy/)
+ + [Policies per account](/docs/alerts/new-relic-alerts-beta/getting-started/best-practices-alert-policies) - n/a + N/A - 10000 policies + 10K policies
- **Alert conditions:** + Alert conditions - - -
Matched data points per minute, per account ([learn more](#query-limit))
+ + Alert query scan operations per minute, per account ([learn more](#query-scan-limit)) - 2,500,000,000 + 2.5B
+ + [Condition name](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-alert-conditions)
+ + [Conditions per policy](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-alert-conditions)
+ + - [Alert conditions per account](/docs/alerts/create-alert/create-alert-condition/alert-conditions) + [Alert conditions per account](/docs/alerts/create-alert/create-alert-conditioN/Alert-conditions) @@ -159,11 +161,14 @@ Limits and rules pertaining to New Relic : - 4000 conditions + 4K conditions
+ + [Targets (product entities)](/docs/new-relic-solutions/get-started/glossary/#alert-target) per condition - 5000 targets for NRQL conditions - 1000 targets for non-NRQL conditions + 5K targets for NRQL conditions + 1K targets for non-NRQL conditions
+ + [Thresholds](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-thresholds-trigger-alert) per condition
- **Alert incidents:** + Alert incidents - - -
[Custom incident descriptions](/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions) - 4000 characters + 4K characters
+ + [Duration for condition incident](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-thresholds-trigger-alert)
+ + Incidents per issue - 10,000 incidents + 10K incidents Incidents beyond this limit will not be persisted.
+ + Incident search API: page size - 1000 pages (25K incidents) + 1K pages (25K incidents) Only use the `only-open` parameter to retrieve all open incidents. If you have more than 25K open incidents and need to retrieve them via the REST API, contact support. @@ -267,31 +277,25 @@ Limits and rules pertaining to New Relic :
- - **Workflows:** - + Workflows - - -
[Workflows per account](/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows) - n/a + N/A - Initial limit 1000 + Initial limit: 1K
+ + Workflow filter size - 4096 characters per workflow + 4,096 characters per workflow
- - **Notification channels (Legacy):** - + Notification channels (Legacy) - - -
Channel limitations