Repository navigation
[Chore] Prometheus 알림 룰을 레포로 편입하고 PodNotReady 오탐 수정 - #460
Merged
Merged
Conversation
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters: 2
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
📊 테스트 커버리지 리포트
|
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.
🧾 요약
semosan-app-alertsPrometheusRule 을 레포로 편입해 ArgoCD 관리로 전환하고, 종료된 Pod 을 장애로 오탐하던PodNotReady룰을 수정🔗 이슈
✨ 변경 내용
k8s/monitoring/prometheusrule.yaml신규 추가. 기존 알림 6개(HighErrorRate,HighResponseTime,JvmHeapHigh,PodRestart,PodNotReady,HighDbConnectionUsage)를 클러스터 현재 상태 그대로 가져왔다PodNotReady에만 phase 필터를 추가했고 나머지 5개는 expr·for·labels·annotations 를 그대로 보존했다k8s/kustomization.yaml에 등록🐛 고치는 문제
종료된 Pod 은 당연히 Ready 가 아니므로 기존 룰에 그대로 걸렸다. 실제로 155일 된 Completed Pod(
postgres-6f46dfddf8-zkcck)과 Evicted Pod(minio-56d777b8db-49kph)이 계속 critical 알림을 발생시키고 있었고, 두 Pod 을 정리하자 알림이 해제됐다critical 알림이 상시 떠 있으면 진짜 장애가 노이즈에 묻힌다. #455 의 MinIO 장애 당시에도 이 알림은 이미 떠 있는 상태였다
and on(namespace,pod) kube_pod_status_phase{phase="Running"} == 1로 좁히는 방법도 있지만 ImagePullBackOff(phase=Pending)를 놓친다. #455 에서 실제로 겪은 장애를 못 잡는 룰이 되므로unless로 종료 상태만 제외했다✅ 확인