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 beginBefore setting up an alert policy, ensure you have an appropriate notification channel.
Create an alert for paused backup plansTo 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:
Go to the Logs Explorer page.
Enter the following filter criteria in the Query pane:
logName="projects/PROJECT_ID/logs/gkebackup.googleapis.com%2Fbackup_plan_change"
resource.type="gkebackup.googleapis.com/BackupPlan"
resource.labels.backup_plan_id=BACKUP_PLAN"
resource.labels.location="LOCATION"
jsonPayload.inputBackupPlan.backupSchedule.paused="true"
Replace the following:
PROJECT_ID: the ID of your Google Cloud project.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.
resource.labels.backup_plan_id and resource.labels.location fields from the filter.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.
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.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.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-07 UTC.
[[["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-08-07 UTC."],[],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4