Fortinet black logo

User Guide

Long-running incidents

24.1.0
Copy Link
Copy Doc ID af1daa65-c273-11ec-9fd1-fa163e15d75b:618492
Download PDF

Long-running incidents

Long-running incidents are incidents with a duration of 7 days or more. The confirmation check frequency for these incidents are automatically scaled back. See the following table:

Incident Duration

Change to Schedule

7 days

Set to 60 minutes

30 days

Set to 1440 minutes

60 days

Pause check

90 days

The underlying metric or metrics will automatically be paused and the incident will be resolved.

For example, if an incident has remained active for 7 days, the confirmation check frequency will be changed to 60 minutes, overriding the configured check frequency for the metric. Once the duration reaches 30 days, the frequency will be changed to 1440 minutes. After 60 days, confirmation checks will be paused.

Note: The frequency changes only apply to confirmation checks. Original checks will still be run until the 60-day mark where further checks will be paused.

Long-running incidents

Long-running incidents are incidents with a duration of 7 days or more. The confirmation check frequency for these incidents are automatically scaled back. See the following table:

Incident Duration

Change to Schedule

7 days

Set to 60 minutes

30 days

Set to 1440 minutes

60 days

Pause check

90 days

The underlying metric or metrics will automatically be paused and the incident will be resolved.

For example, if an incident has remained active for 7 days, the confirmation check frequency will be changed to 60 minutes, overriding the configured check frequency for the metric. Once the duration reaches 30 days, the frequency will be changed to 1440 minutes. After 60 days, confirmation checks will be paused.

Note: The frequency changes only apply to confirmation checks. Original checks will still be run until the 60-day mark where further checks will be paused.