-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compactor" track number of times table compactions were skipped consecutively #11604
Merged
sandeepsukhani
merged 2 commits into
grafana:main
from
sandeepsukhani:track-skipped-compactions-consecutively
Jan 8, 2024
Merged
compactor" track number of times table compactions were skipped consecutively #11604
sandeepsukhani
merged 2 commits into
grafana:main
from
sandeepsukhani:track-skipped-compactions-consecutively
Jan 8, 2024
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
Trivy scan found the following vulnerabilities:
|
ashwanthgoli
reviewed
Jan 8, 2024
ashwanthgoli
approved these changes
Jan 8, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. minor naming suggestion
Co-authored-by: Ashwanth <[email protected]>
rhnasc
pushed a commit
to inloco/loki
that referenced
this pull request
Apr 12, 2024
…cutively (grafana#11604) **What this PR does / why we need it**: Earlier we had a counter for the number of times tables were skipped by compaction due to them being locked by retention. Counter makes it hard to reliably write an alert without making it noisy. I am changing the counter to gauge which would count the number of times tables were consecutively skipped by compaction. This would make it easier to write alerts. **Checklist** - [x] Tests updated --------- Co-authored-by: Ashwanth <[email protected]>
JoaoBraveCoding
added a commit
to JoaoBraveCoding/loki
that referenced
this pull request
Oct 25, 2024
metric was changed in grafana#11604
JoaoBraveCoding
added a commit
to JoaoBraveCoding/loki
that referenced
this pull request
Oct 25, 2024
metric was changed in grafana#11604
6 tasks
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 / why we need it:
Earlier we had a counter for the number of times tables were skipped by compaction due to them being locked by retention. Counter makes it hard to reliably write an alert without making it noisy. I am changing the counter to gauge which would count the number of times tables were consecutively skipped by compaction. This would make it easier to write alerts.
Checklist