Managing Performance Thresholds › How Incidents Open and Close

How Incidents Open and Close

The management console opens network and server incidents when the 5-minute average for a network or server metric exceeds the threshold.

The management console automatically closes an incident when:

• One full clock hour (from the top of hour to the top of hour) of acceptable performance behavior has transpired.
• The server that is associated with the network or server incident enters a maintenance window. Note that after a scheduled maintenance period ends, the management console can open a new incident, if the performance problem persists.
• The incident is 24 hours old. Note that the management console opens a new incident if the performance problem persists.

You can also Acknowledge an incident to indicate your awareness of the issue. In the following example, the management console opened a network incident on the 191.168.1.0/24 network at 7:05 a.m. After 7:20 a.m., there were no subsequent network threshold violations, so the management console closed the incident at 9:00 a.m. Note that because the management console closes incidents at the top of hour, when you Acknowledge an incident, the report also marks the hour (from the top of hour) before the incident, which is 7:00 a.m., to show the time frame of the incident:

If you have set OLAs for availability, the management console opens a server incident when an application is rated Unavailable.

More information:

Managing Application Availability

Schedule Server Maintenance

How Application Performance is Rated