APM metric condition and NRQL condition notification duplication in New Relic alert policies

Goal: Configure a New Relic alert policy that includes both an APM metric condition and an NRQL condition so that a single underlying issue generates one actionable notification instead of multiple noisy alerts. The policy can attach notification channels at the condition level or share a common set at the policy level, and New Relic offers violation closure, minimum duration, and aggregation settings to suppress transient spikes. However, it is unclear whether the platform treats a violation that satisfies both conditions as separate events that each trigger their own notification, or whether it aggregates them into a single notification when the channels are shared. This ambiguity affects teams trying to balance signal fidelity with noise reduction when using mixed condition types.

• Does New Relic send a separate notification for each condition when both fire for the same violation, even if they share the same notification channel?
• Can enabling the “Notify on policy” option or setting a shared aggregation window guarantee that only one notification is delivered per violation?
• If duplicate notifications occur, what configuration (e.g., muting per‑condition channels, using a single policy‑level channel, or custom NRQL aggregation) reliably eliminates the duplication without suppressing legitimate alerts?