Custom Incidents

Incidents are comparable to error conditions. Incidents are raised when predefined conditions are met (for example, when performance drops below a certain minimum threshold for a certain length of time and a service target violation is triggered).

Custom incidents are different in that they are not incidents that are detected by Performance Manager. They are incidents that are detected by users and manually logged into Performance Manager. Custom incidents that override system-detected incidents can be defined. Custom incidents are typically used to manually override incidents such as service target violations with custom incidents that have the Severity set to Informational, which resets service target violations; or the severity setting Service Target Violation, which sets a service target violation. Custom incidents are implemented project wide and cannot be assigned to specific rules.

Custom incidents are logged on the Custom Incidents page. (Performance Manager > Configuration > Custom Incidents).

The Custom Incidents Page

The Custom Incidents page lists all custom incidents that occur during the time period selected using the calendar tool.

The beginning-time and end-time of each custom incident is listed in the From and To columns.
The duration of each custom incident is listed in the Duration column.
The error type (Service Target Violation, Error, Warning or Informational) is listed in the Type column.

Custom incidents can be sorted by column (Name, From, To, Duration, and Type) by clicking the column names or the Ascending/Descending arrow links. To change sort-order-by-column from ascending to descending (and vice-versa), click the appropriate Ascending/Descending arrow links.

To view detailed information of a specific custom incident, click the Report icon of the incident you want to view in Monitoring > Incidents. The Incident report also enables you to jump directly to the relevant time slot within the health report when the incident occurred.