Ignore objects in breakdown reports that have not yet been monitored in the selected period #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Misses support for postgresql. Should we merge anyway? |
Yeah, go for it! |
To be honest, I don't know why a future state should be used for a certain period in the past.
Peviously, the entire time was simply returned as 100 percent available. This applies to objects that have not yet been monitored in the selected period.
nilmerg
force-pushed
the
sla-100-although-not-monitored
branch
from
dcf2ab7
to
067daa8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, objects that had not yet been monitored in the selected period were incorrectly reported with a SLA of 100 percent.
ref/NC/725496
refs #57