Analyzing a CI's critical failures - Documentation for BMC TrueSight Infrastructure Management 11.3.04
After service components and associated functions are identified, you need to monitor their status to analyze their effects and watch for failures. To do so, perform the following tasks:
Severity level values are listed in the following table:
Severity level index
Severity level | Definition |
|---|---|
Severe | Permanently disabling |
Significant | Critical end-user dissatisfaction |
Moderate | Causes degradation of service |
Minor | Causes inconvenience to end user |
Slight | Caused annoyance for customer |
Minimal | Not noticeable by end user |
- Assign a frequency or occurrence level to each failure.
Occurrence level index values are listed in the following table:
Occurrence level index
Occurrence level | Definition |
|---|---|
High | High change of occurrence and needs immediate attention |
Frequent | Frequent change to happen and needs attention |
Moderate | Moderate change to consider prevention |
Occasional | Occasionally might happen |
Slight | Slight chance to happen |
Remote | Unlikely to happen |
Sample of failure modes effects and analysis
- Component–Message Transfer Agent (MTA)
- Function–Routes and converts messages
- Point of failure–Queue length size growing
- Issue type–Performance
- Cause of failure–Network connection failure, receiving MTA failure, problem on sending or receiving computer
- Effect of failure–Remote recipients will not receive an email message while MTA is down
- Severity–Significant
- Occurrence–Slight
- Prevention–Monitoring of the system, network, and exchange services
- Detection–PATROL NT and Exchange parameters related to the issue
