Hey @lukeburden! Looks like a couple things are happening here to cause this to happen.
First, the Incident Preference setting on the policy for the incident you linked is By Policy, meaning that New Relic will create a new incident for the first violation in that policy, but if any other violations occur while the first incident is still unresolved, New Relic won’t send further notifications.
Second, there hasn’t been a time on this incident where it had an opportunity to close. The culprit here is this Synthetics monitor that didn’t close until 10:40am:
By the time that monitor went back to normal at 10:40am, another violation had occurred at 10:01am that is still open:
So from New Relic Alerts perspective, this is all part of the same incident because of the overlap, and that there hasn’t been a moment for this policy where there hasn’t been a violation occurring since it opened this morning.
Getting more emails about these kind of situations is an easy fix though! Now we loop back to the Incident Preference setting; if we use By Condition instead of By Policy, New Relic will send notifications and start incidents for each individual condition you have inside that policy. If Condition 1 violates and then Condition 2 violates, you’ll get an email for both. If during that time a different entity that Condition 1 monitors also violates(think one condition monitoring multiple APM apps), you would not get a third notification.
I recommend taking a look through the Incident Preference guide linked here to read about the options available to you and for best practices on what would be the best option for you in your situation. Let us know if you have any questions!