You also have the opportunity to give some subservices more importance than other subservices. You do this by assigning a number which indicates how much more important a particular service should be than the other contributing subservices (2 = twice as important, 3 = three times as important). Change the weight for database, below, and watch how it affects the severity of the shopping cart service.Get the details!
The Shopping Cart Service using
the rule has a
severity of: 
|
||||||||
|---|---|---|---|---|---|---|---|---|
| Subservice | Subservice Severity |
Weight |
Factor | 
|
|
|
|
|
| Operating System | 
|
1 | 1 | 0 | 1 | 1 | 1 | 1 |
| Applications | 
|
1 | 1 | 0 | 0 | 1 | 1 | 1 |
| Database | 
|
1 | 0 | 0 | 0 | 0 | 1 | |
| Shopping Cart Service Messages |
|
1 | 1 | 0 | 0 | 0 | 1 | 1 |
| Subservice severity ratings | 0 | 0.25 | 0.5 | 0.75 | 1 | |||
| Using the single threshold rule, all thresholds chosen for this example are 0.6. | 0.6 | 0.6 | 0.6 | 0.6 | 0.6 | |||
The weight is a number you select that shows the importance of one subservice compared to the others. All subservices have a default weight of 1 (one). A subservice's weight indicates how much the severity of that subservice should contribute to the total severity. The weighting factor is calculated by dividing each subservices's weight by the total number of contributing services. In this example there are four contributing subservices. If one subservice is given a weight of 2 (two), the factor for that subservice will be equal to 2 divided by 5, that is, 0.4. All other subservices will have a factor of 0.2. (1 divided by 5).
The weight is set in the Subordinates or Superordinates tab.