DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
View Events Video Library
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Integrating PostgreSQL Databases with ANF: Join this workshop to learn how to create a PostgreSQL server using Instaclustr’s managed service

Mobile Database Essentials: Assess data needs, storage requirements, and more when leveraging databases for cloud and edge applications.

Monitoring and Observability for LLMs: Datadog and Google Cloud discuss how to achieve optimal AI model performance.

Automated Testing: The latest on architecture, TDD, and the benefits of AI and low-code tools.

Related

  • The Serious Stack Behind Salesforce Developers — Part 2
  • 2-Tier Architecture vs 3-Tier Architecture in DBMS
  • The Differences Between a Service Catalog, Internal Developer Platform, and PaaS
  • Developing Your Criteria for Choosing APM Tool Providers

Trending

  • Agile Estimation: Techniques and Tips for Success
  • What Is Good Database Design?
  • Unleashing the Power of Microservices With Spring Cloud
  • Freedom to Code on Low-Code Platforms
  1. DZone
  2. Data Engineering
  3. Databases
  4. 10 Ways to Find Your Alerting Sweet Spot with New Relic

10 Ways to Find Your Alerting Sweet Spot with New Relic

Fredric Paul user avatar by
Fredric Paul
·
May. 22, 15 · Interview
Like (0)
Save
Tweet
Share
2.56K Views

Join the DZone community and get the full member experience.

Join For Free

[This article was written by Asami Novak]

Last week New Relic announced a number of exciting updates to our Software Analytics Platform, including a new streamlined alerting system designed to help users focus on fixing problems and eliminate “alert fatigue” with incident rollups.

As part of our reimagined alerting, New Relic now groups related alerts from multiple products into an incident dashboard, allowing the people responsible to better understand the history of a performance outage and more quickly determine how to fix it. Whether you’re focused on servers, databases, Web applications, or mobile apps, you can find the information you need all in one centralized location.

To help new and existing users get up to speed with our new alerting system, we put together a handy checklist of 10 Ways to Get the Most Out of New Relic Alerts. Here are a few suggestions to get you started, but be sure to check out all 10 tips to really find your alerting sweet spot:

1. Define alert policies. Your alert policies define the conditions for when you or your team get notified of an event exceeding the thresholds you select. An alert policy can apply to one or more New Relic products. It can also contain one or more alert conditions and one or more notification channels. When designing your alert policies, consider:

  • The parts of your infrastructure that need personnel to be responsible for them
  • The individuals who are responsible for one or more parts of your infrastructure

2. Create alert conditions. Define one or more conditions to identify what triggers an alert for your selected policy. Each condition applies to a specific New Relic product. For example, you can create a single alert policy with a condition for error rate thresholds for all apps monitored by New Relic APM, a second condition with a custom metric for selected apps monitored by New Relic APM, and a third condition with a CPU percentage threshold for servers monitored by New Relic Servers.

New Relic Alerts chart

[click to enlarge]

3. Use meaningful names. Make sure each alert policy and alert condition has a concise and meaningful name. Doing so means that you can see useful information in notification messages that have limited characters, such as email subject lines, chat, etc. It can also help make it easier to skim the index in the New Relic alerting user interface.

Here are a couple alert policy naming recommendations:

  • Your group or team’s name
  • The set of resources or services the alert policy is targeting

And here are a couple alert condition recommendations:

  • Use camel case or dotted-decimal notation
  • Describe the essence of what threshold is being violated

For additional New Relic alerting tips, take a look at the free checklist, 10 Ways to Get the Most Out of New Relic Alerting.

Want more user tips on New Relic Alerts?

  • Watch this webinar: New Relic Alerts Reimagined
  • Read the documentation for the New Relic Alerts Beta
mobile app Database teams Infrastructure Web Service Documentation History (command) Interface (computing)

Published at DZone with permission of Fredric Paul, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • The Serious Stack Behind Salesforce Developers — Part 2
  • 2-Tier Architecture vs 3-Tier Architecture in DBMS
  • The Differences Between a Service Catalog, Internal Developer Platform, and PaaS
  • Developing Your Criteria for Choosing APM Tool Providers

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends: