• /
  • EnglishEspañolFrançais日本語한국어Português
  • Log inStart now

Understand compound alert events

|View as Markdown

When a compound alert condition's trigger expression evaluates to true, New Relic opens a compound alert event. The event includes a link to your runbook URL. To view specific threshold breaches for each component condition, click through to the individual alert events.

Alert events and issue correlation

Compound alert conditions create multiple related alert events:

  • Multiple alert events: A compound alert condition creates its own compound alert event. By default, each component condition also creates its own alert events when it breaches its thresholds. To reduce noise, you can silence these events from the alert condition's configuration. If you silence a component condition's alert events, that condition's tags won't appear in the compound alert event.
  • Issue correlation: To ensure all related alert events (both compound and component) are grouped into the same issue, configure your component conditions to use the same policy as your compound alert condition. This allows New Relic's issue correlation to group them together.
  • Related events: From a compound alert event, you can navigate to the individual component alert events to see threshold breaches and metrics for each condition.

Custom titles and descriptions

If you set a title or description template on a compound alert condition, that customization carries over to the issue it generates:

  • Issue title: The issue's title displays the rendered text from the compound condition's title template, instead of the default system-generated heading.
  • Issue description: The rendered text from the compound condition's description template appears directly under the alert events section for the compound condition.

To keep the issue page focused, descriptions from individual component (child) conditions aren't displayed there — only the compound condition's description is shown.

Impacted entities

When your component conditions share matching facets (for example, the same service or host), New Relic surfaces the matching entities in the Impacted entities section at the bottom of the issue page. If the shared facets match multiple entities, all of them appear, not just one.

Hover over or click any entity card to view key health and performance metrics for that entity, such as response time, throughput, and error rate.

Copyright © 2026 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.