[[["이해하기 쉬움","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-08-07(UTC)"],[],[],null,["# Set up alerts on RPO risk status of backup plans\n\nAutopilot Standard\n\n*** ** * ** ***\n\nThis page describes how to set up alerts on the RPO risk level and risk reason of\nbackup plans that are based on the\n[log events emitted by Backup for GKE](/kubernetes-engine/docs/add-on/backup-for-gke/how-to/platform-logging-backup-for-gke)\nfrom the Logs Explorer.\n\nIn the context of disaster recovery or business continuity planning,\n*recovery point objective (RPO)* means the most recent point in time from\nwhich data must be restored. It specifies the maximum loss of data due to an\ninfrastructure failure, which is expressed as the amount of time, before the\nfailure, in which write activity is lost.\n\nThe **RPO risk level** column indicates the current level of the backup plan's RPO risk.\nThe risk reason field gives details of why the backup plan is at a specific risk level.\n\nBoth the RPO risk level and risk reason have a many-to-one mapping, that is,\nan RPO risk level of 4 can have multiple reasons why it is that number. For a\ncomplete list of RPO risk levels and corresponding reasons, see the following\ntable.\n\nMapping between RPO risk levels and risk reasons\n------------------------------------------------\n\nBefore you begin\n----------------\n\nBefore you set up an alert policy, ensure you have an appropriate\n[notification channel](/monitoring/support/notification-options).\n\nCreate an alert\n---------------\n\nFor more information about creating general log-based alert policies, see\n[Configure log-based alerting policies](/logging/docs/alerting/log-based-alerts). Or, to\ncreate an alert policy specifically for RPO risk level or RPO risk reasons\nchanges in backup plans, do the following:\n\n1. Go the Logs Explorer page.\n [Go\n to Logs Explorer](https://console.cloud.google.com/logs/query)\n\n2. In the **Query** pane, enter the following filter criteria:\n\n logName=\"projects/\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/logs/gkebackup.googleapis.com%2Fbackup_plan_change\"\n resource.type=\"gkebackup.googleapis.com/BackupPlan\"\n resource.labels.backup_plan_id=\"\u003cvar translate=\"no\"\u003eBACKUP_PLAN\u003c/var\u003e\"\n resource.labels.location=\"\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e\"\n jsonPayload.backupPlanMetadata.rpoRiskLevel\u003e=\"\u003cvar translate=\"no\"\u003eVALUE\u003c/var\u003e\"\n jsonPayload.backupPlanMetadata.rpoRiskReason=\"\u003cvar translate=\"no\"\u003eREASON\u003c/var\u003e\"\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of your Google Cloud project.\n - \u003cvar translate=\"no\"\u003eBACKUP_PLAN\u003c/var\u003e: the name of the backup plan for which you want to generate alerts.\n - \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: the [compute region](/compute/docs/regions-zones#available) of the backup plan for which you want to generate alerts. For example, `us-central1.`\n - \u003cvar translate=\"no\"\u003eVALUE\u003c/var\u003e: The RPO risk level value for the backup plan you want to be alerted on. The valid values are in the range \\[1,5\\]. We recommended setting up alerts on risk level \\\u003e= 4.\n - \u003cvar translate=\"no\"\u003eREASON\u003c/var\u003e: (Optional) Select an appropriate risk reason from the [table](#mapping-rpo-level-to-reason).\n3. To validate the query, click **Run Query**.\n\n4. In the **Query results** toolbar, expand the **Actions** menu and select\n **Create log alert**.\n\n5. In the **Alert details** pane, enter a name for your alerting policy in the\n **Alert Policy Name** field. For example, `Alert for RPO risk level of backup\n plan`.\n\n6. Select an option from the **Policy severity level** menu. Incidents and\n notifications display the severity level. We recommend setting the severity\n level to **Critical**.\n\n7. Enter a description for your alerting policy. You can also include\n information that might help the recipient of a notification diagnose the\n problem. For information about how you can format and refine the content of\n this field, see\n [Using Markdown and variables in documentation templates](/monitoring/alerts/doc-variables).\n\n8. Click **Next**.\n\n9. Set the **Time between notifications** and **Incident autoclose duration**.\n We recommend setting the time between notifications to one day and the autoclose duration to seven\n days.\n\n10. Click **Next**.\n\n11. Select one or more notification channels for your alerting policy.\n\n12. Click **Save**.\n\n After you save the policy, you receive alerts to your notification\n channels when a backup plan matches your filter."]]
