When key performance indicators spike or drop, individuals and teams in your organization need to be notified. New Relic provides coordinated alerting tools that allow you to focus on the metrics that you care about the most, so you can address the underlying problems before they reach your end users.
Both versions operate from the same concepts and structure:
- The legacy alerting system at rpm.newrelic.com provides everything you need to identify alerting scenarios that matter to you and respond to notifications about critical situations with your apps, servers, and key transactions.
- New Relic Alerts (accessed directly at alerts.newrelic.com) provides enhanced features and functionality to support the suite of New Relic products.
Access to the specific alerting system depends on the New Relic product and your subscription level.
Customize your alerting scenarios
To customize your alerting scenarios, refer to New Relic's recommended best practices. Take into consideration:
- Why you want to be alerted (policy)
- What criteria will trigger an alert (conditions)
- When do your selected metric levels escalate into alerting situations (thresholds)
- Who needs to be notified about the situation, and how are they notified (channels)
Give the alerting scenario a name (policies)
- The parts of your organization and resources that need personnel to be responsible for them
- The individuals who are responsible for one or more parts of your architecture
Identify criteria to trigger an alert (condition)
Each alert policy can contain as many conditions as you need. An alert condition includes three components:
- New Relic product (APM, Browser, etc.) and type of condition (metric, external service, etc.)
- Entities that the policy targets, such as apps monitored by New Relic APM or New Relic Browser, hosts monitored by New Relic Infrastructure, etc.
- Thresholds that escalate into alerting situations with increasing severity
Set severity levels (thresholds) to escalate alerts
Your alert condition defines escalating severity levels (thresholds) to trigger an alert, including a required Critical (red) level and an optional Caution or Warning (yellow) level. Thresholds for every alert condition include:
- What metric to monitor (Apdex, response time, CPU usage, custom metrics, etc.)
- What value it tracks (count, average, etc.)
- What time frame elapses before triggering an alert notification
The color-coded health status indicator in the user interface changes as the alerting threshold escalates or returns to normal. This allows you to monitor a situation through New Relic's UI before a Critical threshold passes, without needing to receive specific notifications about it.
For example, you can define a Critical (red) alert that notifies you when the error percentage for your app is above 10 percent at least once in any five minute period. You can also define an optional Caution or Warning (yellow) alert with different criteria.
Use New Relic's user interface to create thresholds for your policy conditions in the legacy alerting system or for New Relic Alerts as applicable for your New Relic subscription.
Decide who is notified and how (channels)
New Relic offers a variety of notification channels that you can tailor to each alerting situation. For example, you may want product team members to view alert notifications through a company HipChat room, but you want your Network Operations Center to monitor Critical (red) alerts through webhooks. This gives you the flexibility to decide not only who but how to be notified about alerting situations.
View alert incident or event details
After you set up one or more alert policies that define alert conditions for your New Relic product entities, New Relic monitors the conditions you have defined. Depending on the threshold level and notification channel, you will receive alert notifications.
You can also view the alert incident or event details directly from the New Relic user interface. For example, you can see the color-coded health status indicator for an affected app from the Applications index, and select details from the Recent events.
To view additional information about incidents or events from the user interface:
- Legacy alerting system: From rpm.newrelic.com, select APM, Browser, or Servers, select the app or host, and then select Events > Alerts. OR, select Alerts > Alert history.
- New Relic Alerts (Alerts New): From alerts.newrelic.com, select Incidents or Events.
Manage your alerting structure
Owners and Admins
To view or update your alert policy configuration from the user interface:
- Legacy alerting system: From rpm.newrelic.com, select APM, Browser, or Servers, then select Alerts > (selected policy type).
- New Relic Alerts (Alerts New): From alerts.newrelic.com, select Alert policies.
Use New Relic's alert APIs
In addition to using New Relic's user interface to set up and maintain your alerting structure, you can use API calls as applicable to the alerting system.