Stay organized with collections
Save and categorize content based on your preferences.
Autopilot
Standard
This page describes how to set up alerts for the paused backup plans based on
the logs viewable from the Logs Explorer.
Backup plans can be paused automatically or manually as listed in the
Pause a backup schedule.
To receive notifications when critical backup plans are paused, it's important
to set up alerts. This procedure is similar to configuring alerts for failed
backups. For instructions, see Set up alerts for failed backups.
Before you begin
Before setting up an alert policy, ensure you have an appropriate
notification channel.
Create an alert for paused backup plans
To create general log-based alert policies, see Configure log-based alerts.
Or, to create an alert policy specifically for Backup for GKE paused backup plans:
BACKUP_PLAN: the name of the backup plan for which
you want to generate alerts.
LOCATION: the compute region of the
backup plan for which you want to generate alerts. For example, us-central1.
Click Run query to validate the query.
In the Query results toolbar, expand the Actions menu and select Create log alert.
In the Alert details pane, enter a name for your alerting policy in
the Alert Policy Name field. For example, alert for paused backup plan.
Select an option from the Policy severity level drop-down. Incidents
and notifications display the severity level. We recommend setting the
severity level to Critical.
Enter a description for your alerting policy. You can also include
information that might help the recipient of a notification diagnose the
problem. For information about how you can format and refine the content
of this field, see Using Markdown and variables in documentation templates.
Click Next.
Set the Time between notifications and Incident autoclose duration.
We suggest setting notification to one day and autoclose duration to seven days.
Click Next.
Select one or more notification channels for your alerting policy.
Click Save.
After you save the policy, you receive alerts to your notification channels whenever a backup plan matching your filter is paused.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Set up alerts for paused backup plans\n\nAutopilot Standard\n\n*** ** * ** ***\n\nThis page describes how to set up alerts for the paused backup plans based on\nthe logs viewable from the Logs Explorer.\n\nBackup plans can be paused automatically or manually as listed in the\n[Pause a backup schedule](/kubernetes-engine/docs/add-on/backup-for-gke/how-to/backup-plan#pause).\nTo receive notifications when critical backup plans are paused, it's important\nto set up alerts. This procedure is similar to configuring alerts for failed\nbackups. For instructions, see [Set up alerts for failed backups](/kubernetes-engine/docs/add-on/backup-for-gke/how-to/alerts).\n\nBefore you begin\n----------------\n\nBefore setting up an alert policy, ensure you have an appropriate\n[notification channel](https://cloud.google.com/monitoring/support/notification-options).\n\nCreate an alert for paused backup plans\n---------------------------------------\n\nTo create general log-based alert policies, see [Configure log-based alerts](/logging/docs/alerting/log-based-alerts).\nOr, to create an alert policy specifically for Backup for GKE paused backup plans:\n\n1. Go to the Logs Explorer page.\n\n [Go to Logs Explorer](https://console.cloud.google.com/logs/query)\n2. Enter the following filter criteria in the **Query** pane:\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\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eBACKUP_PLAN\u003c/span\u003e\u003c/var\u003e\"\n resource.labels.location=\"\u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e\"\n jsonPayload.inputBackupPlan.backupSchedule.paused=\"true\"\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\n backup plan for which you want to generate alerts. For example, us-central1.\n\n | **Note:** If you want to set up alerts for any backup plans across all locations, then you can omit the `resource.labels.backup_plan_id` and `resource.labels.location` fields from the filter.\n3. Click **Run query** to validate the query.\n\n4. In the **Query results** toolbar, expand the **Actions** menu and select **Create log alert**.\n\n5. In the **Alert details** pane, enter a name for your alerting policy in\n the **Alert Policy Name** field. For example, alert for paused backup plan.\n\n6. Select an option from the **Policy severity level** drop-down. Incidents\n and notifications display the severity level. We recommend setting the\n severity 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\n of this field, see [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 suggest setting notification to one day and autoclose duration to seven days.\n\n | **Note:** A notification is only triggered when a backup plan status changes to **paused**. A single status change will generate a single notification. If the backup plan becomes active and then pauses again, a new notification will be sent only after 24 hours have passed since the previous notification.\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 channels whenever a backup plan matching your filter is paused."]]