• Log inStart now

How alert condition violations are closed

This document explains the different ways violations can be closed.

How violations automatically close

A violation will automatically close when the targeted signal returns to a non-violating state for the time period indicated in the condition's thresholds. This wait time is called the recovery period.

For example: If the violating behavior is "Apdex score below 0.80 at least once in 5 minutes," then the violation will automatically close when the Apdex score is equal to or higher than .80 for 5 consecutive minutes. The same applies to a "for at least x minutes" threshold: x minutes of non-violating behavior are required to automatically close the violation.

When a violation closes automatically:

  1. The closing timestamp is backdated to the start of the recovery period.
  2. The evaluation resets and restarts from when the previous violation ended.

All conditions have a violation time limit setting that will automatically force-close a long-lasting violation.

Manually close a violation

You can manually close an open violation. This is useful, for example, when a signal has violated the threshold, but it no longer exists and also doesn't have a violation time limit. (A time limit would automatically close a long-lasting violation.)

To close a violation:

  1. Go to the open violation you want to close.
  2. Click Manually close violation.

To close all violations associated with a condition:

  1. Go to the condition you want to close.
  2. Disable the condition and then re-enable it.


An incident will close automatically when all of its associated critical violations have been closed.

Set a time limit for long-lasting violations

The violation time limit setting will automatically force-close a long-lasting violation after the number of days/hours you select. This is most useful for ephemeral entities that, when they disappear, cause a continual violation that won't automatically close.

Limits and Defaults

  • All alert violations will have a violation time limit applied to them. Most alert conditions will allow you to edit this field.
  • The default value, if one is not supplied during configuration, is 3 days (24 hours for Infrastructure conditions).
  • The violation time limit for non-Infrastructure conditions can be set as low as 5 minutes, and as high as 30 days. If, for some reason, the signal is still violating in 30 days, the violation will close, and a new violation will open. Infrastructure conditions can be set to the following hours: 1, 2, 4, 8, 12, 24, 48, or 72.


This setting is related to the inactive issue setting.

When the time periods in these two settings are different, our system uses the shorter time period, regardless of the setting. For example, if the close open violation time setting is 2 days and the inactive issue time setting is 3 days, our system would wait 2 days before closing the issue.


  • You set the violation time limit to 12 hours. If that violation lasts for 12 hours, it will be closed at 12 hours and the condition's evaluation of that entity will be reset.
  • Your JVM has a CPU spike and this creates a violation. The JVM then crashes and is replaced by a new JVM. If you have not set a violation time limit, the crashed JVM’s violation will never close.
Copyright © 2022 New Relic Inc.

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