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).
Incidents are closed when the conditions that raise them are no longer active. Conditions that raise incidents are configured when monitors are configured. See Transaction Conditions for details.
See Custom Incidents for information regarding custom incidents.
See Adding Rules for information regarding defining service target incidents.
The Incidents tab () includes the following information for each incident:
When the Incidents log contains more entries than can be included on a single page, entries are broken out over multiple pages. The Result Page number links (available at both the top and bottom of the page) allow you to jump to alternate result pages-simply click a page number. You can tell how many results out of the total you're currently viewing by the entries tag (for example, "entries 1-100 of 1920").
The incidents log can become unwieldy when too many results are returned for a specified time period. You can filter down the incidents list to the incident names and types that are most relevant using the Use filter "Any name" and "Any severity" lists. Select an incident name and type from the lists and click Update.
Incidents in the incident log can also be sorted by column (From, To, Duration, Name, or Severity). Click the column names or the Ascending/Descending arrow links to have results sorted by that column. To change sort-order-by-column from ascending to descending (or vice-versa) click the appropriate Ascending/Descending arrow link.