To add a custom incident:
-
On the
Projects page (), click the project for which you want to add a custom incident.
-
On the
Custom Incidents tab (), click
Add Custom Incident.
The
Add Custom Incident page appears.
-
Enter a name for the custom incident in the
Incident Name field.
-
Enter a description of the custom incident in the
Description field.
-
Specify start and end times for the incident using the
From and
To lists.
-
Specify whether the custom incident should override system-detected health monitoring results for the same time period by
checking the
Override System incidents check box.
-
Select an appropriate severity for the custom incident from the
Severity list.
-
Informational: This is the lowest severity and is color-coded blue. This severity is used to mark incidents that do not indicate system
problems. Although it can be used for rules, it is more likely to be used for custom incidents (for example,
maintenance work or
invalid results).
- Warning: Color-coded yellow, this severity is used to define lower thresholds and offers early warning of potential problems. This
is less likely to be used for custom incidents.
- Error: Color-coded red, this severity is used for critical thresholds when immediate action is required. This severity is not likely
to be linked to a
log only action.
- Service Target Violation: This severity is also color-coded red. This is a special type of error that is used as the basis for service target agreement
statistics calculation. When a service target incident is active, a system is considered to be in a state where the service
target of the service provider is in violation of agreed upon quality standards (for example, response times or availability).
Service target statistics include:
-
Click
Save to save the custom incident.