How alert condition violations are closed

This document explains the different ways New Relic Alerts violations can be closed.

How violations automatically close

A violation will automatically close when the targeted data source returns to a non-violating state for the time period indicated in the condition's thresholds.

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 is closed, the evaluation resets and starts over from when the previous violation ended.

Some types of alert 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. One reason you may want to do this: a data source has violated, but it no longer exists and also doesn't have a violation time limit (which would close a long-lasting violation).

To close a violation:

  1. Find the open violation you want to close.
  2. Select Manually close violation.

To close all violations associated with a condition:

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

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

Set a time limit for long-lasting violations

Some types of alert conditions have a violation time limit setting. This limit will automatically force-close a long-lasting violation after the number of hours you select. This is most useful for ephemeral entities that, when they disappear, cause a continual violation that won’t automatically close.

Examples:

  • 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.

For more help

Recommendations for learning more: