Halaman ini menjelaskan cara melihat log audit untuk cadangan otomatis
instance Cloud SQL Anda.
Anda dapat menggunakan log audit untuk melakukan hal berikut:
Lihat log audit untuk memverifikasi apakah pencadangan berhasil diselesaikan.
Konfigurasikan pemberitahuan berbasis log untuk memberi tahu Anda tentang status pencadangan.
Melihat log audit
Anda dapat menggunakan konsol Google Cloud , gcloud CLI, atau
API untuk melihat log audit guna memverifikasi apakah pencadangan berhasil
diselesaikan dalam periode pencadangan.
Konsol
Di Google Cloud konsol, pilih Logging, lalu pilih Logs Explorer.
Ganti PROJECT_ID dengan ID Google Cloud project Anda.
Ekspresi pertama memfilter log audit Peristiwa Sistem.
Ekspresi kedua memfilter log audit untuk
pencadangan otomatis. Ekspresi akhir memfilter log audit untuk
instance Cloud SQL.
Untuk mengetahui informasi selengkapnya tentang cara menggunakan konsol Google Cloud untuk mengkueri
log audit, lihat
Melihat log.
Lihat status pencadangan yang dibuat selama periode pencadangan. Status ini
ditampilkan di kolom windowStatus. Untuk melihat kolom ini, selesaikan langkah-langkah berikut:
Ganti PROJECT_NAME dengan nama project Google Cloud Anda.
Ekspresi pertama memfilter log audit Peristiwa Sistem.
Ekspresi kedua memfilter log audit untuk
pencadangan otomatis. Ekspresi akhir memfilter log audit untuk
instance Cloud SQL.
Informasi selengkapnya tentang cara menggunakan gcloud untuk mengkueri
log audit, lihat
Melihat log.
Lihat status pencadangan yang dibuat selama periode pencadangan. Status ini
ditampilkan di kolom windowStatus.
API
Sebelum menggunakan salah satu data permintaan,
lakukan penggantian berikut:
PROJECT_ID: ID Google Cloud project Anda.
Untuk meminta isi JSON, ekspresi pertama memfilter
log audit Peristiwa Sistem. Ekspresi kedua memfilter log audit untuk pencadangan otomatis.
Ekspresi akhir memfilter log audit untuk instance Cloud SQL.
Informasi selengkapnya tentang cara menggunakan API untuk mengkueri log
audit, lihat Melihat log.
Metode HTTP dan URL:
POST https://logging.googleapis.com/v2/entries:list
Meminta isi JSON:
{
"resourceNames": [
"projects/PROJECT_ID"
],
"pageSize": 5,
"filter": "logName=projects/PROJECT_ID/logs/cloudaudit.googleapis.com%2Fsystem_event AND protoPayload.methodName = cloudsql.instances.automatedBackup AND resource.type=cloudsql_database",
"orderBy": "timestamp desc"
}
Untuk mengirim permintaan Anda, perluas salah satu opsi berikut:
curl (Linux, macOS, atau Cloud Shell)
Simpan isi permintaan dalam file bernama request.json,
dan jalankan perintah berikut:
Untuk mengetahui informasi selengkapnya tentang LOG_ENTRY_UNIQUE_IDENTIFIER
untuk kolom insertId, lihat
LogEntry.
Lihat status pencadangan yang dibuat selama periode pencadangan. Status ini
ditampilkan di kolom windowStatus.
Status pencadangan otomatis
STATUS_SUCCEEDED: Pencadangan otomatis berhasil
diselesaikan.
STATUS_ATTEMPT_FAILED: Cloud SQL mencoba membuat
cadangan, tetapi pencadangan tidak dimulai atau gagal. Alasan
status ini mencakup:
Cadangan lain sedang berjalan pada instance.
Lokasi pencadangan dibatasi oleh kebijakan organisasi Anda.
Pencadangan instance selesai, tetapi terjadi error.
Instance tidak berjalan saat Cloud SQL mencoba membuat
cadangan.
STATUS_FAILED: Pencadangan otomatis instance
belum berhasil diselesaikan atau tidak dapat diselesaikan dalam
periode pencadangan.
Misalnya,
jika Anda mengaktifkan pencadangan otomatis
dan menjadwalkan periode pencadangan antara pukul 01.00 dan 5.00, pencadangan
mungkin akan gagal jika Anda memiliki banyak operasi EXPORT selama jangka waktu tersebut.
Pencadangan otomatis juga dapat gagal jika terlalu banyak konflik dengan operasi EXPORT yang berjalan dalam waktu lama.
Jika Cloud SQL mencoba membuat cadangan beberapa kali selama
periode pencadangan, tetapi cadangan tidak dapat dibuat karena alasan yang tercantum untuk STATUS_ATTEMPT_FAILED, Cloud SQL akan membuat log audit lain dengan
kolom windowStatus yang ditetapkan ke STATUS_FAILED.
STATUS_SKIPPED: Instance Cloud SQL berhenti berjalan
sejak berhasilnya pencadangan terakhir. Oleh karena itu, pencadangan otomatis baru
tidak dibuat.
Jika pencadangan memiliki status STATUS_SUCCEEDED, Anda
akan diberi tahu untuk tujuan pelacakan.
Jika cadangan memiliki status STATUS_FAILED atau STATUS_ATTEMPT_FAILED
Anda akan diberi tahu untuk melakukan tindakan korektif, berdasarkan pesan yang muncul di entri log. Anda juga dapat
melakukan pencadangan yang sesuai dengan permintaan
sebelum jadwal periode pencadangan berikutnya.
Jika pencadangan memiliki status STATUS_SKIPPED, Anda akan
diberi tahu untuk memulai ulang instance Cloud SQL.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-09 UTC."],[],[],null,["\u003cbr /\u003e\n\n[MySQL](/sql/docs/mysql/backup-recovery/view-audit-logs-for-automated-backups \"View this page for the MySQL database engine\") \\| [PostgreSQL](/sql/docs/postgres/backup-recovery/view-audit-logs-for-automated-backups \"View this page for the PostgreSQL database engine\") \\| SQL Server\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis page describes how to view an audit log for an automated backup of your\nCloud SQL instance.\n\nYou can use audit logs to do the following:\n\n- View an audit log to verify whether the backup is completed successfully.\n- Configure a log-based alert to notify you of the backup's status.\n\nView an audit log\n\nYou can use the Google Cloud console, [gcloud CLI](/sdk/gcloud), or\nAPI to view an audit log to verify whether a backup is completed\nsuccessfully within a backup window. \n\nConsole\n\n1. In the Google Cloud console, select **Logging** and then select **Logs Explorer**.\n\n [Go to Logs Explorer](https://console.cloud.google.com/logs/query)\n2. To filter for audit logs for\n automated backups of Cloud SQL instances, run the following query:\n\n ```bash\n logName=\"projects/\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/logs/cloudaudit.googleapis.com%2Fsystem_event\"\n protoPayload.methodName=\"cloudsql.instances.automatedBackup\"\n resource.type=\"cloudsql_database\"\n ```\n\n Replace \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e with your Google Cloud project's ID.\n\n The first expression filters for [System Event audit logs](/logging/docs/audit#system-event).\n The second expression filters for audit logs for\n automated backups. The final expression filters for audit logs\n for Cloud SQL instances.\n\n For more information about how to use the Google Cloud console to query\n for audit logs, see\n [View logs](/sql/docs/sqlserver/audit-logging#viewing_logs).\n3. View the status of a backup created during the backup window. This status is\n displayed in the `windowStatus` field. To view this field, complete the following steps:\n\n 1. Click the audit log.\n 2. Click the `metadata` field.\n\ngcloud\n\n1. To filter for audit logs for\n automated backups of Cloud SQL instances, run the following query:\n\n ```bash\n gcloud logging read \\\n \"logName=projects/\u003cvar translate=\"no\"\u003ePROJECT_NAME\u003c/var\u003e/logs/cloudaudit.googleapis.com%2Fsystem_event\n AND protoPayload.methodName=cloudsql.instances.automatedBackup AND\n resource.type=cloudsql_database\" \\ \n --project=PROJECT_NAME\n ```\n\n Replace \u003cvar translate=\"no\"\u003ePROJECT_NAME\u003c/var\u003e with your Google Cloud project's name.\n\n The first expression filters for [System Event audit logs](/logging/docs/audit#system-event).\n The second expression filters for audit logs for\n automated backups. The final expression filters for audit logs\n for Cloud SQL instances.\n\n For more information about how to use `gcloud` to query\n for audit logs, see\n [View logs](/sql/docs/sqlserver/audit-logging#viewing_logs).\n2. View the status of a backup created during the backup window. This status is\n displayed in the `windowStatus` field.\n\nAPI\n\n\nBefore using any of the request data,\nmake the following replacements:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: The ID of your Google Cloud project.\n\nFor the request JSON body, the first expression filters for [System Event audit logs](/logging/docs/audit#system-event). The second expression filters for audit logs for automated backups.\nThe final expression filters for audit logs for Cloud SQL instances.\n\nFor more information about how to use the API to query for audit\nlogs, see [View logs](/sql/docs/sqlserver/audit-logging#viewing_logs).\n\n\nHTTP method and URL:\n\n```\nPOST https://logging.googleapis.com/v2/entries:list\n```\n\n\nRequest JSON body:\n\n```\n{\n \"resourceNames\": [\n \"projects/PROJECT_ID\"\n ],\n \"pageSize\": 5,\n \"filter\": \"logName=projects/PROJECT_ID/logs/cloudaudit.googleapis.com%2Fsystem_event AND protoPayload.methodName = cloudsql.instances.automatedBackup AND resource.type=cloudsql_database\",\n \"orderBy\": \"timestamp desc\"\n} \n```\n\nTo send your request, expand one of these options:\n\ncurl (Linux, macOS, or Cloud Shell) **Note:** The following command assumes that you have logged in to the `gcloud` CLI with your user account by running [`gcloud init`](/sdk/gcloud/reference/init) or [`gcloud auth login`](/sdk/gcloud/reference/auth/login) , or by using [Cloud Shell](/shell/docs), which automatically logs you into the `gcloud` CLI . You can check the currently active account by running [`gcloud auth list`](/sdk/gcloud/reference/auth/list).\n\n\nSave the request body in a file named `request.json`,\nand execute the following command:\n\n```\ncurl -X POST \\\n -H \"Authorization: Bearer $(gcloud auth print-access-token)\" \\\n -H \"Content-Type: application/json; charset=utf-8\" \\\n -d @request.json \\\n \"https://logging.googleapis.com/v2/entries:list\"\n```\n\nPowerShell (Windows) **Note:** The following command assumes that you have logged in to the `gcloud` CLI with your user account by running [`gcloud init`](/sdk/gcloud/reference/init) or [`gcloud auth login`](/sdk/gcloud/reference/auth/login) . You can check the currently active account by running [`gcloud auth list`](/sdk/gcloud/reference/auth/list).\n\n\nSave the request body in a file named `request.json`,\nand execute the following command:\n\n```\n$cred = gcloud auth print-access-token\n$headers = @{ \"Authorization\" = \"Bearer $cred\" }\n\nInvoke-WebRequest `\n -Method POST `\n -Headers $headers `\n -ContentType: \"application/json; charset=utf-8\" `\n -InFile request.json `\n -Uri \"https://logging.googleapis.com/v2/entries:list\" | Select-Object -Expand Content\n```\n\nYou should receive a JSON response similar to the following:\n\nResponse \n\n```\n{\n \"entries\": [\n {\n \"protoPayload\": {\n \"@type\": \"type.googleapis.com/google.cloud.audit.AuditLog\",\n \"status\": {\n \"message\": \"OK\"\n },\n \"authenticationInfo\": {},\n \"requestMetadata\": {\n \"requestAttributes\": {},\n \"destinationAttributes\": {}\n },\n \"serviceName\": \"cloudsql.googleapis.com\",\n \"methodName\": \"cloudsql.instances.automatedBackup\",\n \"resourceName\": \"projects/PROJECT_ID/instances/INSTANCE_NAME\",\n \"metadata\": {\n \"windowStartTime\": \"2022-12-15T13:00:00Z\",\n \"message\": \"\",\n \"windowStatus\": \"STATUS_SUCCEEDED\",\n \"@type\": \"type.googleapis.com/speckle.AutomatedBackupEventLog\",\n \"windowEndTime\": \"2022-12-15T17:00:00Z\",\n \"backupCompletionTime\": \"2022-12-15T14:11:57.347Z\",\n \"backupStartTime\": \"2022-12-15T14:11:16.631Z\"\n }\n },\n \"insertId\": \"LOG_ENTRY_UNIQUE_IDENTIFIER\",\n \"resource\": {\n \"type\": \"cloudsql_database\",\n \"labels\": {\n \"region\": \"REGION_NAME\",\n \"project_id\": \"PROJECT_ID\",\n \"database_id\": \"DATABASE_ID\"\n }\n },\n \"timestamp\": \"2022-12-15T14:11:57.391565Z\",\n \"severity\": \"INFO\",\n \"logName\": \"projects/PROJECT_ID/logs/cloudaudit.googleapis.com%2Fsystem_event\",\n \"receiveTimestamp\": \"2022-12-15T14:11:57.785814800Z\"\n },\n ],\n}\n```\n\n\u003cbr /\u003e\n\nFor more information about \u003cvar translate=\"no\"\u003eLOG_ENTRY_UNIQUE_IDENTIFIER\u003c/var\u003e\nfor the `insertId` field, see\n[LogEntry](/logging/docs/reference/v2/rest/v2/LogEntry).\n\nView the status of a backup created during the backup window. This status is\ndisplayed in the `windowStatus` field.\n\nAutomated backup statuses\n\n- `STATUS_SUCCEEDED`: The automated backup is completed successfully.\n- `STATUS_ATTEMPT_FAILED`: Cloud SQL tried to create the\n backup, but the backup either didn't start or it failed. Reasons\n for this status include:\n\n - Another backup is running on the instance.\n - The backup location is restricted by your organization policy.\n - The backup of the instance completed, but an error occurred.\n - The instance wasn't running when Cloud SQL tried to create the backup.\n- `STATUS_FAILED`: The automated backup of the instance either\n hasn't completed successfully or can't be completed within the\n backup window.\n\n For example,\n if you enabled automated backups\n and scheduled the backup window for between 1:00 am and 5:00 am, your backup\n might fail if you have many `EXPORT` operations during this time frame.\n Automated backups might also fail if there are too many conflicts with an `EXPORT` operation that runs for a long time.\n\n If Cloud SQL tries to create a backup multiple times during a\n backup window, but the backup can't be created for the reasons listed for `STATUS_ATTEMPT_FAILED`, Cloud SQL generates another audit log with\n the `windowStatus` field set to `STATUS_FAILED`.\n- `STATUS_SKIPPED`: The Cloud SQL instance [stopped running](/sql/docs/sqlserver/start-stop-restart-instance)\n since the last successful backup. Therefore, a new automated backup\n wasn't created.\n\nConfigure a log-based alert\n\nYou can [configure a log-based alert](/logging/docs/alerting/log-based-alerts) to\nnotify you of the backup's status.\n\n- If a backup has a `STATUS_SUCCEEDED` status, you can be notified for tracking purposes.\n- If a backup has the `STATUS_FAILED` or `STATUS_ATTEMPT_FAILED` status, you can be notified to take corrective action, based on the message that appears in the log entry. You can also take an [on-demand backup](/sql/docs/sqlserver/backup-recovery/backing-up) before the next scheduled backup window.\n- If a backup has a `STATUS_SKIPPED` status, you can be notified to restart the Cloud SQL instance.\n\nWhat's next\n\n- [Learn more about backing up your data](/sql/docs/sqlserver/backup-recovery/backups).\n- [Learn more about creating and managing backups](/sql/docs/sqlserver/backup-recovery/backing-up).\n- [Learn more about restoring data](/sql/docs/sqlserver/backup-recovery/restore).\n- [See how to restore your data from a backup](/sql/docs/sqlserver/backup-recovery/restoring#restorebackups).\n- [See how to perform a point-in-time recovery](/sql/docs/sqlserver/backup-recovery/restore#tips-pitr)."]]
