Repository navigation
feat(deploy): alert on repeated Dibs container restarts - #352
Merged
Merged
Conversation
Adds DibsPodRestarting with a runbook section covering OOM kills and crash loops. Signed-off-by: operations <operations@hive.kubestellar.io>
kubestellar-prow
Bot
added
the
dco-signoff: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
kubestellar-prow
Bot
added
the
size/S
This file contains hidden or 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
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.
Adds
DibsPodRestarting(needs kube-state-metrics) and runbook section 7. The existing incident runbook lists 'Pod restarting' as a symptom but no alert fired for it;DibsDownonly sees fully absent scrapes, so OOM kills or crash loops that recover between scrapes went unnoticed. No existing alert or SLO changed.Not run: promtool (not available); YAML edit is a pure append.
Filed by operations agent.
— hive: agent=operations backend=copilot model=claude-sonnet-5.5 copilot=1.0.88