Repository navigation
chore: PagerDuty 개통 — 원장 ID 기록 - #321
Merged
Merged
Conversation
pagerduty.py setup 결과. 이메일·API 키·연동 키는 넣지 않았다. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Test Coverage
|
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.
pagerduty.py setup을 실행한 결과를env/prod.json에 기록합니다.POF6OPH: 1차 담당에게 먼저 울리고, 10분 안에 ACK가 없으면 팀원에게 갑니다. 2회 반복합니다.PQ9NRPTsns.pagerduty = ruleup-prod-pagerduty: 서울·버지니아 모두 HTTPS 구독이 확인됐습니다.이메일, API 키, 연동 키는 넣지 않았습니다. 머지와 상관없이, 로컬의 이 원장으로
p0_p1.py prod를 실행하면 P0 경보에 PagerDuty 토픽이 붙습니다.🤖 Generated with Claude Code