In the world of DevOps and microservices, where new services are deployed on a monthly, weekly, or even daily basis, IT operations teams often find it hard to monitor and apply consistent alert conditions on these new applications. Manually keeping track of all the new applications and individually applying specific alerting policies is time consuming and not scalable. To address those issues, we have introduced dynamic targeting support in New Relic Alerts.

What does dynamic targeting for apps do?

Instead of selecting each app one by one and manually applying an alert policy on it, you can now target new apps using labels in New Relic Alerts. Dynamic targeting constantly looks for applications that have the appropriate labels, and then automatically applies the alerting condition to those applications.

For instance, if you want to ensure that any application deployed in your production environment abides by production performance standards, you can create an APM alert condition with an Environment:Production label. This alert condition will be applied to any application that gets instantiated with an Environment:Production label, without requiring any additional input from the ops team.

apm screenshot

This APM screenshot shows how to set an alert condition using labels to dynamically target applications.

Multiple label combinations are supported

Even better, we enable our customers to combine multiple labels in a single alert policy, and then target applications that contain all the labels in that alert policy. For instance, customers can easily target applications deployed in production by the Ninja team in the East region by just selecting all three labels (Env:Production, Team:Ninja, and Region:East) in their alert policy. Any time a new application with all the three labels is deployed, New Relic Alerts will automatically apply the alert condition to that application. There is no need to create a new label for each combination. Dynamic targeting helps IT ops teams keep their alert policies lean and easy to maintain.

targeted apps diagram

This diagram illustrates how to target applications with multiple labels.

How customers use dynamic alerts targeting

Customers who are frequently spinning up new services in large, dynamic environments find this feature extremely handy. Here are two examples of how customers can use dynamic targeting of alert conditions for apps:

  1. Meeting company/department SLAs: Dynamic targeting makes it easy for New Relic customers to monitor and make sure their apps consistently meet their Service Level Agreements. For instance, if you want to be alerted when any Tier 1 app experiences an error rate of more than 0.5% or an average response time of more than 100ms, this can be easily achieved using dynamic targeting. An alert condition with tier:1 will automatically apply to any application that is deployed as a Tier 1 application.
  1. Default alerts for a team/environment/region: By setting up dynamic targeting ahead of time, customers can create a set of default alert conditions that are automatically applied to their new services as soon as they begin reporting to New Relic. This ensures that new services have basic monitoring coverage from the start. 

Want to learn more?

More information on dynamic targeting for apps instrumented with New Relic APM can be found under the dynamic targeting with labels for apps section of the New Relic documentation website.

Additionally, New Relic Infrastructure offers a similar feature using filter sets. You can read more about that in the Infrastructure and Alerts documentation. Combining these two features allows New Relic customers to build dynamic host and app layer policies, a highly recommended best practice that can significantly reduce alert configuration maintenance.


Chhavi Nijhawan is a senior product marketing manager at New Relic. She is passionate about new technologies. View posts by .

Interested in writing for New Relic Blog? Send us a pitch!