Cloud Billing などの多くの Google Cloud サービスは、 Google Cloud ユーザーと重要な情報を共有するために通知を送信します。デフォルトでは、これらの通知は特定の Identity and Access Management（IAM）ロールを持つメンバーに送信されます。重要な連絡先を使用する場合、独自の連絡先リストを指定することで、通知を受け取るユーザーをカスタマイズできます。イベントの前に連絡先を確認し、必要に応じて変更してください。詳細については、通知の連絡先の管理をご覧ください。
Personalized Service Health を有効にする
Personalized Service Health を使用すると、プロジェクトに関連する Google Cloud サービスの中断を特定し、効率的に管理して対応できます。詳細については、Personalized Service Health の概要をご覧ください。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-04 UTC。"],[],[],null,["# Prepare to resolve issues during your event\n\nHow you respond to, categorize, and solve incidents of differing severity can\nsignificantly affect your operations during an event. Use a centralized incident\nmanagement system for effective tracking throughout the incident lifecycle. For\nmore information, see\n[Manage incidents and problems](/architecture/framework/operational-excellence/manage-incidents-and-problems).\n\nReview best practices when working with Customer Care\n-----------------------------------------------------\n\nWork with your Cloud Customer Care team and your TAM for additional support. If\nyou're [creating a support case](/support/docs/customer-care-procedures), make\nsure to provide detailed and specific information to make it easier for the\nCustomer Care team to respond to you quickly and efficiently. To get\nimmediate attention from Google, consider choosing \"P1\" for the support case\npriority. You can always downgrade the priority later. For more information, see\n[Best practices for working with Customer Care](/support/docs/best-practices).\n\nCreate a communication plan\n---------------------------\n\nEstablish clear incident response procedures including clear roles and\nresponsibilities, communication protocols, and escalation paths. Create a\nvirtual chat room or conference call for cross-collaboration and communication\nbetween teams and vendors so that there's a channel for updates and progress\nreports.\n\nEnsure access\n-------------\n\nResolve any authentication and access issues before your event. Make sure that\nyou have granted the appropriate permissions to users, developers,\noperators, data scientists, security administrators, network administrators, and\nany other roles in your organization. This includes the ability to create\nsupport cases, troubleshoot issues, and access your disaster recovery\nenvironment.\n\nReview your contacts\n--------------------\n\nMany Google Cloud offerings, such as Cloud Billing, send out\nnotifications to share important information with Google Cloud users. By\ndefault, these notifications are sent to members with certain\nIdentity and Access Management (IAM) roles. With Essential Contacts, you can\ncustomize who receives notifications by providing your own list of contacts.\nMake sure to review your contacts ahead of your event and modify them as needed.\nFor more information, see\n[Managing contacts for notifications](/resource-manager/docs/managing-notification-contacts).\n\nEnable Personalized Service Health\n----------------------------------\n\nPersonalized Service Health lets you identify Google Cloud service disruptions\nrelevant to your projects so that you can manage and respond to them efficiently.\nFor more information, see the\n[Personalized Service Health overview](/service-health/docs/overview).\n\nMake sure that you have enabled the Service Health API ahead of your event\nand that your organization can access the dashboard and configure alerts.\nFor more information, see\n[Manage Personalized Service Health access](/service-health/docs/manage-access).\n\nWhat's next\n-----------\n\n- [Optimize your cloud resources](/support/docs/peak-events/optimize-resources)"]]
