Default dashboards to Cortex blocks storage only #302
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
Signed-off-by: Marco Pracucci <marco@pracucci.com>
pracucci
force-pushed
the
default-dashboards-to-blocks-storage
branch
from
fd2f4bf to
1ec012d
Compare
pstibrany
approved these changes
May 12, 2021
You're right, we don't have numbers. Let's say then we do this change to push the blocks storage forward :) |
simonswine
pushed a commit
to grafana/mimir
that referenced
this pull request
Oct 18, 2021
…shboards-to-blocks-storage Default dashboards to Cortex blocks storage only
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.
What this PR does:
With the default config, dashboards both display panels related to Cortex chunks and blocks storage. Given most Cortex users have moved to blocks I propose to change the default to blocks only.
Which issue(s) this PR fixes:
N/A
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]