For these windows or gaps, there are scheduled tasks or commands in place to verify specific metrics or actions within the provider environment. This process generates an alert, which is linked to a corresponding metric; if either one provides a response, it indicates that the resource is operational or that the metric is accurate.

This is evaluated from two perspectives: if the alert returns a 200 status code, it suggests an issue with the metric; conversely, if the metric returns a 200, it confirms that the alert is active and the outcome is correct, as the equipment is reporting its status via that metric. This approach also helps in addressing false positives and connectivity issues, as they can be analyzed from multiple angles.