You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 20, 2022. It is now read-only.
I noticed a major outage of monitoring where around 3k facilities were reported out of order with reason "monitoring disrupted". To fix this, we need to intelligently filter out disruptions:
Facilities that were previously disrupted should still be assumed disrupted even though monitoring is not available at the moment
Facilities that have been active prior to the monitoring outage should be assumed operational
As for calculating the grade and total downtime, there are basically a few cases of which only 2 are relevant:
|-------------------------|
|------------------------>| Case 1: Monitoring dis. only
|------------<----------->| Case 2: Disruption before, resolved after
|-----<------>------------| Case 3: Disruption before and after
|------------>------------| Case 4: Disrupted after
-> monitoring dis only = ignore
-> Case 2 -> we don't know when it really ended; have to include
The text was updated successfully, but these errors were encountered:
I noticed a major outage of monitoring where around 3k facilities were reported out of order with reason "monitoring disrupted". To fix this, we need to intelligently filter out disruptions:
As for calculating the grade and total downtime, there are basically a few cases of which only 2 are relevant:
The text was updated successfully, but these errors were encountered: