Verify TSDB actual retention period #177
Merged
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
* Using configured retention period is not enough as retention storage can cut short retention period. So, we need to check for actual retention period by making a query to up metric to see when is the first metric available. * For emaps provider initialisation, make more attempts to get zones from API just to give more chances to initialise emaps provider. It can help when internet conn is flaky Signed-off-by: Mahendra Paipuri <[email protected]>
* Take into account max number of datapoints limit when making API requests to get real retention period. * Apply middleware to all relevant TSDB end points and get correct query parameter when routing to TSDB backend. Signed-off-by: Mahendra Paipuri <[email protected]>
Signed-off-by: Mahendra Paipuri <[email protected]>
Signed-off-by: Mahendra Paipuri <[email protected]>
mahendrapaipuri
force-pushed
the
fix_ceems_lb_resource_based
branch
from
1c396d3
to
7965efb
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.
Using configured retention period is not enough as retention storage can cut short retention period. So, we need to check for actual retention period by making a query to up metric to see when is the first metric available.
For emaps provider initialisation, make more attempts to get zones from API just to give more chances to initialise emaps provider. It can help when internet conn is flaky