feat(monitoring): add platform stability alerts (JDWLABS-29)#9
Open
jdwillmsen wants to merge 1 commit into
Open
feat(monitoring): add platform stability alerts (JDWLABS-29)#9jdwillmsen wants to merge 1 commit into
jdwillmsen wants to merge 1 commit into
Conversation
Add PrometheusRule platform-stability-rules with alerts for the failure modes behind the instance-manager cascade incident, which previously self-healed and stayed invisible until a build happened to fail: - LonghornInstanceManagerRecreated: instance-manager pod recreated in the last 10m (faults the replicas it served). - LonghornManagerOOMKilled: longhorn-manager hit its memory limit. - VaultNotReady: platform-vault StatefulSet has no ready replicas. - NodeMemoryHigh: node memory above 85%. Vault's own telemetry (vault_core_unsealed) is not currently scraped, so a true seal-while-running alert is left as a follow-up; VaultNotReady covers pod loss, which is how the incident manifested. Verified: all four expressions evaluate against live Prometheus (status=success, 0 firing) and the metrics return series; manifest passes kubectl apply --dry-run=server. Closes JDWLABS-29. Refs JDWLABS-22. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Summary
Proactive alerts for the Longhorn instance-manager cascade failure mode (epic JDWLABS-22) — which self-healed and stayed invisible until a CI build happened to fail and was investigated by hand.
Closes JDWLABS-29.
New PrometheusRule
platform-stability-rules(ns: monitoring)LonghornVolumeFaultedalready exists inlonghorn-rules, so it's not duplicated here.ruleSelectorNilUsesHelmValues: falsemeans the rule is auto-selected.Verification
kubectl apply --dry-run=server: accepted.status=success, 0 firing (cluster healthy), and each underlying metric returns series.Known gap / follow-up
vault_core_unsealedreturned 0 series — Vault'svault-metricsServiceMonitor exists but isn't producing data, so a true seal-while-running alert can't fire yet.VaultNotReady(kube-state) covers pod loss, which is how the incident actually manifested. Fixing Vault metrics scraping → addVaultSealedis noted as a follow-up.🤖 Generated with Claude Code