-
Notifications
You must be signed in to change notification settings - Fork 549
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
fix StuckInCatchup/Bootstrap alerts #14619
Merged
ghost-not-in-the-shell
merged 4 commits into
develop
from
alert/fix-stuck-in-catchup-and-bootstrap
Dec 18, 2023
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
22db7d9
fix StuckInCatchup/Bootstrap alerts
d5a2080
Merge branch 'develop' into alert/fix-stuck-in-catchup-and-bootstrap
ghost-not-in-the-shell 54da920
Merge branch 'develop' into alert/fix-stuck-in-catchup-and-bootstrap
ghost-not-in-the-shell 2513346
Merge branch 'develop' into alert/fix-stuck-in-catchup-and-bootstrap
ghost-not-in-the-shell File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
Just a note: I think this approach may trigger this alert if a node that was in bootstrap exits bootstrap and then re-enters bootstrap again, since the
rate
function in prometheus do not skip breaks in data, they only filter out drops in values. When you apply thesyncStatus
filter here, you are causing a break in the data, but when the data matches the filter again, there will be a massive observed jump in theprocess_update_ms_total
between the breaks, which will still be observed in the final output of this query.Let's merge this for now, as we need a new metric to fix this. Something like
current_sync_status_process_uptime_ms_total
which is a counter that resets every timesyncStatus
changes.