[日本語] 「監視は後回し」のまま本番を走らせていませんか？本パックは、YAMLコピペ【\u003d】5〜10分の設定で最低限の監視と通知を動かせるスターターキットです。Slack通知例・権限と落とし穴・デプロイスクリプトまで同包しています。 同包内容: - monitoring/*.yaml : HTTP 5xx、タスク残存、請求額スパイクの雲形 - scripts/deploy.sh / scripts/verify.sh : 投入・続部確認の雲形 - GUIDE.md、TROUBLESHOOTING.md、README.md、LICENSE.txt - 運用のコツ（開閉値・権限・環境差異チェックリスト） 前提: - IAM: Monitoring Admin / Logging Admin 相当 - gcloud CLI が使用できる環境 使い方 (超最短): 1. YAML内の projectId と通知チャネルを自環境に置換 2. scripts/deploy.sh を実行 3. 関値を一時的に下げてテスト発火し、Slack/メールで到達確認 [English] Running production without proper monitoring? This starter kit lets you get basic monitoring and alerts running in about 5–10 minutes just by copying the YAML templates. It includes Slack notification examples, guidance on permissions and pitfalls, and deploy scripts. Contents: - `monitoring/*.yaml`: templates for HTTP 5xx errors, task queue backlog, and billing cost spike alerts. - `scripts/deploy.sh` / `scripts/verify.sh`: example scripts for deployment and connectivity checks. - `GUIDE.md`, `TROUBLESHOOTING.md`, `README.md`, `LICENSE.txt` - Tips for operation (recommended thresholds, required roles, environment differences checklist). Prerequisites: - IAM roles equivalent to Monitoring Admin / Logging Admin. - Environment where the gcloud CLI is available. Quick start: 1. Replace the `projectId` and notification channel in the YAML files with your own values. 2. Run `scripts/deploy.sh`. 3. Temporarily lower the thresholds to trigger alerts and confirm Slack/email notifications.