Skip to content
This repository has been archived by the owner on Nov 20, 2022. It is now read-only.

Intelligently filter out "monitoring disrupted" times #4

Closed
Akii opened this issue Aug 7, 2018 · 2 comments
Closed

Intelligently filter out "monitoring disrupted" times #4

Akii opened this issue Aug 7, 2018 · 2 comments

Comments

@Akii
Copy link
Owner

Akii commented Aug 7, 2018

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:

  1. Facilities that were previously disrupted should still be assumed disrupted even though monitoring is not available at the moment
  2. 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
@Akii
Copy link
Owner Author

Akii commented Nov 4, 2018

As a quick solution, I've filtered out all "unknown" states from the DB source. This effectively eliminates like 80% of cases described here.

@Akii
Copy link
Owner Author

Akii commented Nov 10, 2018

See #9

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant