This document contains some technical rules and limits for alerts.
- New Relic One pricing plan
See Users and roles.
- Original pricing plan
- Owner and Admins can add, change, disable, and delete alert policies, conditions, and channels.
- Users and Restricted Users can only view alert policies and conditions and their settings.
- Any user role can acknowledge an incident or close a violation.
Sub-accounts do not inherit a master account's alert policies. You must create policies separately for all accounts and sub-accounts.
The following rules apply both to the New Relic One user interface and to the REST API (v2).
|New Relic Alerts||Minimum value||Maximum value|
|Alert policy name||1 character||64 characters|
|Policies per account||n/a||10000 policies|
|Products per policy||any New Relic product (APM, Mobile, Synthetics, etc.)||any New Relic product|
|Condition name||1 character||64 characters|
|Conditions per policy||0 conditions||500 conditions|
|Infrastructure alert conditions||0 conditions||3700 conditions|
Web app response percentiles per account
|0 conditions||4000 conditions|
|Targets (product entities) per condition||1 target||1000 targets from 1 or more products|
|Thresholds per condition||0 Warnings, 1 Critical||1 Warning, 1 Critical|
|Custom violation descriptions||4000 characters|
|Duration for condition violation||
Exception: 1 minute for
|Violations per incident||1 violation||
Violations beyond this limit will not be persisted.
|Violation Search API - Page Size||1 page (less than or equal to 25 violations)||
1000 pages (25K violations)
Only use the
|Notification channel name||1 character||64 characters|
|Channels per account||n/a||
1000 channels per type
Exception: No limits for user channels
|Channel limitations||Depends on channel||Depends on channel|