Create or rename an alert policy

An alert policy can apply to one or more New Relic products (targets or entities). It can also contain one or more alert conditions and one or more notification channels. You can make an alert policy as simple or as complex as your organization requires.

Admins, Owner, or add-on managers: The basic setup process is the same, regardless of which New Relic product (APM, Browser, etc.) uses the alert policy. The types of metrics and thresholds for alert conditions will vary depending on the target.

Best practices for naming alert policies

New Relic recommends three common patterns and practices for structuring and naming alert policies:

  • Targets or resources in your architecture that have people responsible for their well being
  • Teams that are responsible for part of the architecture
  • Individual policies for specific users
Policies organized by... Comments
Architecture

Targets or resources in your organization may have different people responsible for their well-being. Common segments may include the environment type (production, staging, integration, development) or the target or resource type (app server code, client-side code, databases, hosts, etc.).

To make these types of alert policies easier to identify, you can give them names based on your architecture. For example:

  • Product A website (production)
  • Product B website (staging)
  • Mobile product app (iOS)
  • Hosts (production)
  • Databases (production)
Teams Specific teams may be responsible for parts of your architecture. For example, you may want to name their alert policy Team: Site engineering, Team: Website development, etc.
Individuals

Alert policies set up for specific individuals may be useful when they want to personally keep an eye on a particular resource or metric. This provides them the freedom to add and remove conditions as well as adjust thresholds whenever they want, without having to communicate those changes to others.

To make these types of alert policies easier to identify, you can include the person's name in the alert policy; for example, User: John Doe's metrics, User: Jane Doe (production), etc.

Create an alert policy

Admins or Owner

As part of the alert policy workflow in New Relic Alerts, start by giving the policy a meaningful name:

  1. Go to alerts.newrelic.com > Alert policies.
  2. From the Alert policies index, select [plus icon] New alert policy.
  3. Type a meaningful name for the policy (maximum 64 characters).
  4. Select the incident preference.
  5. Select Create alert policy.
  6. Specify the alert conditions for your policy.

You can continue from here to define the alert conditions and assign one or more notification channels. If you decide to continue later, select the alert policy's name from the Alert policies index.

Change a policy's name

Admins or Owner

For your convenience, New Relic Alerts allows you to use the same name for different policies, conditions, and notification channels. If you want to use unique names, review or search the index before adding or changing a name.

To rename an existing alert policy:

  1. Go to alerts.newrelic.com > Alert policies > (select a policy).
  2. Mouse over the policy's name, then select the edit [pencil icon] icon.
  3. Type a meaningful name for the policy (maximum 64 characters), then save.

New Relic Alerts automatically updates any associated alert conditions and notification channels for the policy.

View existing policies

The New Relic Alerts index lists alert policies in alphabetical order. To view or search for existing alert policies:

  1. Go to alerts.newrelic.com > Alert policies.
  2. Use the search box, sort any column, or scroll the list.
  3. To view detailed information, select the policy's name.

To view policy and condition information for a specific entity, select the Settings > Alert conditions page from the entity's New Relic product UI.

For more help

Recommendations for learning more: