Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/how-to/alerts below:

Set up alerts for failed backups | Backup for GKE

Stay organized with collections Save and categorize content based on your preferences.

Autopilot Standard

This page describes how to configure the system so that you will receive alerts when Backup for GKE backups fail.

You can create backups in two different ways:

• By manually creating a Backup resource.
• By configuring a schedule when creating your BackupPlan resource.

As a best practice, create backups using automatic scheduling. However, it can be challenging to keep track of the status for these automatically created backups. You have two choices:

• Periodically view the list of Backup resources, looking for newly failed backups.
• Set up an alert to notify you when backup execution fails.

This page describes how to configure an alert policy based on log events emitted by Backup for GKE and viewable from the Logs Explorer.

Before setting up an alert policy, ensure you have an appropriate notification channel.

To create general log-based alert policies, see Configure log-based alerts. Or, to create an alert policy specifically for Backup for GKE failed backups:

1. Go to the Logs Explorer page

   Go to Logs Explorer

2. Enter the following filter criteria in the Query pane:

   logName="projects/PROJECT_ID/logs/gkebackup.googleapis.com%2Fbackup_change"
   resource.type="gkebackup.googleapis.com/BackupPlan"
   resource.labels.backup_plan_id="BACKUP_PLAN"
   resource.labels.location="LOCATION"
   jsonPayload.changeType="UPDATE"
   jsonPayload.inputBackup.state="FAILED"
   

   Replace the following:

   • PROJECT_ID: the ID of your Google Cloud project.
   • LOCATION: the compute region of the backup plan for which you want to generate alerts.
   • BACKUP_PLAN: the name of the backup plan for which you want to generate alerts.
   Note: This creates an alert policy for any failed backups of a specific backup plan. If you want to create a single policy for all failed backups, omit the resource.labels.backup_plan_id and resource.labels.location fields.

3. Click the Create alert label below the Query pane.

4. Enter a meaningful name for your alert policy and any documentation you want to make available to recipients of alerts.

5. Click Next twice.

6. Set the appropriate notification frequency and autoclose duration. We suggest 5 min and 7 days.

7. Click Next.

8. Select the appropriate notification channels and save your alert policy.

After you save the policy, you receive alerts to your notification channels when a backup matching your filter fails.

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