Calculation Blackout Periods about nr1-slo-r HOT 5 OPEN

We have operating hours of 7am-8pm, anything outside this time would not be included in the SLO.

from nr1-slo-r.

@ricegi @tangollama is it enough to provide user some timepicker where blackout hours will be set? Or this should be much more complex to define more than one blackout period? Could you please provide some use case for this?

from nr1-slo-r.

@norbertsuski there are two use cases for this. The first is more straightforward. The second more complex and based on what @jeffrey-hines is driving at.

1. I intentionally took down a system for maintenance last Friday for 1 hour. I want to be able to specify that time period as "out of scope" towards my SLO attainment goals. (i.e. don't penalize myself for an intentional, scheduled, presumably contractually valid maintenance window). That's the goal of this issue.
2. @jeffrey-hines is referencing a very different idea - that there are operating hours for a compute service outside of which the SLO attainment is invalid. Supporting that feature would be far more involved, and - to be honest - outside of my view of what is universally valuable in a cloud computing service. Let's move that request to a new issue.

@jeffrey-hines, could you perhaps explain the use case you're highlighting further in a new issue?

from nr1-slo-r.

So the first point looks pretty similar to this one: #16 ?

from nr1-slo-r.

In was thinking of adding this to the SLO configuration - like a section to handle blackout periods in the calculation.

from nr1-slo-r.