...
You can think of the KPI Scores like a report card, the student (node) has received 10/10 for English (reachability), 10/10 for Maths (availability) and so on. The KPI Scores in the screenshot above come from the polled data and are scored out of the weighted value, this weighted value is a percentage, so in the configuration file it is 0.1 which means it is 10% or a maximum possible KPI score of 10/10. The table below shows the configuration value and the resulting KPI Score value.
| KPI Item | Configuration Item | Configured Weighting | Maximum KPI Score |
|---|---|---|---|
| Reachability | weight_reachability | 0.1 | 10 (10%) |
| Availability | weight_availability | 0.1 | 10 (10%) |
| Response | weight_response | 0.2 | 20 (20%) |
| CPU | weight_cpu | 0.2 | 20 (20%) |
| Memory | weight_mem | 0.1 | 10 (10%) |
| Interface | weight_int | 0.3 | 30 (30%) |
Because they are not present in all node types, there are two additional KPI values which overload onto the Memory and Interface KPI values these are, Swap and Disk, these split the weighting of each into half and track that seperatelyseparately, e.g. Interface KPI by default is 30%, so when the Disk KPI is present the Interface KPI gets a value of 15% and the Disk KPI gets a value of 15%. So the table would like like this when all 8 KPI's are present, as they are for Linux Servers.
| KPI Item | Configuration Item | Configured Weighting | Maximum KPI Score |
|---|---|---|---|
| Reachability | weight_reachability | 0.1 | 10 (10%) |
| Availability | weight_availability | 0.1 | 10 (10%) |
| Response | weight_response | 0.2 | 20 (20%) |
| CPU | weight_cpu | 0.2 | 20 (20%) |
| Memory | weight_mem | 0.1 x 50% | 5 (5%) |
| Swap | weight_mem | 0.1 x 50% | 5 (5%) |
| Interface | weight_int | 0.3 x 50% | 15 (15%) |
| Disk | weight_int | 0.3 x 50% | 15 (15%) |
The result is that all the maximum KPI Score for a node will be 100 or 100%.
...
If we want to know WHY the health from the front page is 92.2% we can look at all the KPI values, like the Disk KPI of 10.50/15, CPU KPI is 19.98/20 and SWAP KPI is 4.75/5, we can take 100% and subtract the remainders so,
| KPI Item | KPI Score | Remainder Calculation | Health Remainders |
|---|---|---|---|
| Reachability | 10/10 | 10 - 10 | 0 |
| Availability | 10/10 | 10 - 10 | 0 |
| Response | 20/20 | 20 - 20 | 0 |
| CPU | 19.98/20 | 20 - 19.98 | 0.02 |
| Memory | 2.04/5 | 5 - 2.04 | 2.96 |
| Swap | 4.75/5 | 5 - 4.75 | 0.25 |
| Interface | 15/15 | 15 - 15 | 0 |
| Disk | 10.5/15 | 15 - 10.5 | 4.5 |
Adding together the Health Reduction results and subtracting from 100 gives us: 100 - (0.02 + 2.96 + 0.25 + 4.5) = 92.27%
...
NMIS KPI Scores are a powerful way to get to the bottom of the health of your infrastructure, they will assist to see where resources are being used and assist to identify operational problems very fast.