Home
| Pattern | Rule name | Description |
|---|---|---|
 |
All down | All tests for all sites are unknown. This typically happens when the data store cannot be accessed. |
 |
Site down | All tests for a particular site are unknown. This can happen if the site is down (check ping), the test service is down or the firewall is misconfigured. |
 |
Site can't test | All tests initiated by a particular site are unknown. This can happen if the archive service is down, the scheduling service is doing, the configuration is faulty or the outgoing firewall rules are misconfigured. |
 |
Site cannot be tested | All tests to a particular site that are remotely initiated are unknown. This can happen if the ingoing firewall rules are misconfigured. |
 |
Site mostly can't test | 70% of all tests initiated by a particular site are unknown. |
 |
Site mostly can't be tested | 70% of all tests to a particular site that are remotely initiated are unknown. |
| Pattern | Rule name | Description |
|---|---|---|
 |
Outgoing tests failure | 70% or more failures where this site is the source. Soft failures (yellow) are counted as a half. Missing data is excluded from the count. |
 |
Incoming tests failure | 70% or more failures where this site is the destination. Soft failures (yellow) are counted as a half. Missing data is excluded from the count. |